DjangoBot: #django-dev

(worksforme is usually the right status there)

mm thanks I know need to find the ticket for which I asked more info :)

iep, found it, Timeline rocks

jacobkm: as you're around, will you be the nice guy to add estonian to global_settings.py? (diff in #7141 settings.diff)

telenieko: yeah, I'll do it in a few -- I'm in the middle of something

ok don't worry, I'll take a look at Lithuanian by the way ;)

lt > Lithuanian, also for global_settings when you can ;)

axiak: http://code.djangoproject.com/ticket/2070#comme...

In English, month names are always uppercase ?

telenieko: yes.

Thanks.

telenieko: et is now in global_settings.

Nice, and lt ?

telenieko: lt == Lithuanian, yeah?

yes

adding now.

#7458 you can close it when you commit the global_settings

That leaves us with two translation tickets left, one is likely to be closed and the other is in jezdez hands, hurray :) and newforms-admin only introduces 5 new strings :))

telenieko: done

thanks!

telenieko: you mean the german thing?

#7477?

jezdez: that one

ok, is on the todo list

there's no hurry, until 2nd September :)

:)

telenieko: have you seen #5522?

I'll play around with msgfmt --statistics to see which translators to blame during summer, hehe.

telenieko: hehe

jezdez: nope, There are atleast two tickets about those two commands (one is mine) I have to crawl my mail I think Malcolm told me somebody was working on them.

yup, me :)

:))

what is django/conf/locale/messages.mo ?

I had a thorough look at babel today, since I somehow find it weird how make-messages works

hm, dunno

why?

Nothing, it's some nasty file I created somehow. I thought it came from svn ;)

but it was created running make-messages.py -a

I think not too many people run it with -a :)

I can't find the ticket I filled for make-messages "once upon a time", it was about make-messages changing the Created-Date instead of last changed. Just in case you work on it ;)

well, this is what I feel should be changed in make-messages. if there is an error in its inner loop, it leaves the translator with filename.ext.py files

oh, no, not that one actually :/

jezdez: #6106

I've filled 38 ticket since I started using django :)))))

has there been some discussion about the fate of localflavor, btw?

not that I'm aware of

The last think I remember about localflavour was on The Roadmap, but I'm not sure what jacob told about it.

882 translated string + 92 unstranslated make up a complete translation of Django in case you were curious ;)

Anything above 882 has msgid copied over msgstrs!

good to know

maby we should keep a log about that

about the magic number? msgfmt --statistics es/LC_MESSAGES/django.po :)

I think I will follow malcoms idea and look at #6106 once #5522 is merged

jezdez: #5522 looks awesome; if you want to add **New in Django development version** flags to all the new commands I can check it in.

w00t

will do

jacobkm: did you see my mail about my brand new super cow powers?

telenieko: yeah, I dunno why that is. I'm gonna fool around and look... for now try to to break anything :P

Am I the only super cow? I try to keep my mouse out of the right of the screen to not touch the "big red button" hehe

There's a couple of Trac admins; I might have just added you to that group to save time.

telenieko: OK, seems I can't let you batch modify without letting you do those other things, too. So just be caareful, OK?

jacobkm: I changed a lot of "make-messages.py" in the continous text to "django-admin.py makemessages" (also with compile-messages). should I keep those changes and add **New in Django development version**?

jacobkm: I promise to be carefull. Thanks

jezdez: maybe the first time you use it put a note in warning about the change. Thereafter you can just use the new version.

great, will do

i have a question, i am working on #6587 and i wonder about #3349, was thinking about combining that into my patch but just wondering if the solution with wrapping the exeption in a function is a good idea.

[530]_: I'm -1 to the patch on #3349; this sort of exception monkeypatching really is nasty. I agree that Python's ImportError is a bit broken (and if you look at the python-dev archives you can see that many agree) but working around it in this way... ugh.

[530]_: note that #3349 's patch also touches the exceptions of other loaders.

but it can be done by just raising with the traceback like raise ImportError, "Could not import settings '%s' (Is it on sys.path? Does it have syntax errors?): %s" % (self.SETTINGS_MODULE, e), get_prev_traceback()

if i'm not wrong

like this http://dpaste.com/57423/, or is this still monkeypatching?

or skip this patch alltogether

one ticket less for 1.0 :)

[530]_: It seems a bit less monkey ;)

jacobkm: added new patch to #5522

some manpages are scheduled to die then :o

midnight! time to sleep. Good night all¡!

night telenieko

jezdez: Hi. So do yopu know if is #5522 going to land on trunk before 1.0?

Yeah, I'm pretty sure jacobkm said he was going to look at putting it in after jezdez added the latest patch

jezdez, Alex_Gaynor : because I had been getting a translation 'coverage' statistics fetching script similar to make-messages reviewed by Malcom and it was almost ready. I could refactor it to make use of the new laout of things after the move to the management commands infrastructure