I'm using http://babel.edgewall.org/ exactly for that purpose. Works
extremely well. There are even some Django-specific extensions at
http://babel.edgewall.org/wiki/BabelDjango (I don't use them though).
On Aug 18, 4:48 pm, Joost Cassee <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> A Farsi-localized
Hi devs,
Happily there's ihooks.py that does 99% of work (and a bit more).
Please see ticket and applied patch: http://code.djangoproject.com/ticket/8413
Working for me on windows and linux.
Also one can use the patch to track wrong imports, and it might be
useful to add warn() to tell people t
On Aug 19, 8:32 pm, "Yuri Baburov" <[EMAIL PROTECTED]> wrote:
> Hi devs,
>
> Happily there's ihooks.py that does 99% of work (and a bit more).
>
> Please see ticket and applied patch:http://code.djangoproject.com/ticket/8413
> Working for me on windows and linux.
Hmmm, I thought one had to be c
On Tue, Aug 19, 2008 at 5:55 PM, Graham Dumpleton
<[EMAIL PROTECTED]> wrote:
> On Aug 19, 8:32 pm, "Yuri Baburov" <[EMAIL PROTECTED]> wrote:
>> Hi devs,
>>
>> Happily there's ihooks.py that does 99% of work (and a bit more).
>>
>> Please see ticket and applied patch:http://code.djangoproject.com/t
On Aug 19, 1:39 am, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> (And you know, I still think we'd be better off with
> "django-YES-THIS-ONE" and "django-NO-THE-OTHER-ONE". Or perhaps a tad
> more seriously, something like "django-community" and "django-core" —
> otherwise we'll be fighting this batt
On Wed, Aug 20, 2008 at 12:37 AM, Simon Willison <[EMAIL PROTECTED]>wrote:
>
> On Aug 19, 1:39 am, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> > (And you know, I still think we'd be better off with
> > "django-YES-THIS-ONE" and "django-NO-THE-OTHER-ONE". Or perhaps a tad
> > more seriously, somethin
On Tue, Aug 19, 2008 at 8:10 AM, Mike Scott <[EMAIL PROTECTED]> wrote:
> I'm definately +1 on the idea. Also moving this to a seperate thread to
> raise awareness.
*Sigh*
Please don't.
Seriously - this comes up every couple of months, and it's just a
bikeshed argument. We get about one off-topi
*sigh*
Please take this thread to django-users. This list is for the internal
development of django and this thread doesn't contribute to that.
After all, the last half a dozen times such a thread was started (and
I'm sure you carefully did your research before proposing it yet again),
it wasn't
On Tue, Aug 19, 2008 at 6:12 PM, Yuri Baburov <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 19, 2008 at 5:55 PM, Graham Dumpleton
> <[EMAIL PROTECTED]> wrote:
>> On Aug 19, 8:32 pm, "Yuri Baburov" <[EMAIL PROTECTED]> wrote:
>>> Hi devs,
>>>
>>> Happily there's ihooks.py that does 99% of work (and a bit
On Tue, Aug 19, 2008 at 8:16 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
> Please take this thread to django-users. This list is for the internal
> development of django and this thread doesn't contribute to that.
Done.
--~--~-~--~~~---~--~~
You received thi
any reason, why it´s currently impossible to use "initial" with
inlineformset_factory. is it planned to integreate this feature?
thanks,
patrick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gro
On Tue, Aug 19, 2008 at 12:10 PM, patrickk <[EMAIL PROTECTED]> wrote:
>
> any reason, why it´s currently impossible to use "initial" with
> inlineformset_factory. is it planned to integreate this feature?
I guess I am failing to see how this is useful? initial data in an
inline model formset is b
usecase:
let´s say you have a "booking" (form) with a number of X "booking
amounts" (formset). now the user could be able to save a pre-defined
template for common bookings. these templates are saved as "template"
and "template amounts". so, if the user selects a given template, the
template-amoun
On Tue, Aug 19, 2008 at 12:22 PM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>Seems
> a bit overkill for the general case due to the unknown size of the
> queryset.
It is possible to specify both a queryset and initial data with a
ModelFormSet or InlineModelFormSet, and initial will override the
que
Uh.. disregard that. My mistake. I read the code wrong and
BaseInlineFormSet does not take **kwargs and pass them to
BaseModelFormSet.__init__(), so no you can't specify 'initial'. Which
is good.
-Justin
On Tue, Aug 19, 2008 at 12:54 PM, Justin Fagnani
<[EMAIL PROTECTED]> wrote:
> On Tue, Aug 19
now this question is probably better posted in django-users, but:
is there any way to prepopulate an unbound formset using
inlineformset_factory?
thanks,
patrick
On Aug 19, 10:05 pm, "Justin Fagnani" <[EMAIL PROTECTED]>
wrote:
> Uh.. disregard that. My mistake. I read the code wrong and
> BaseIn
Hi all,
I've organized the testing sprint in Israel this Sunday and it was a
great experience. The idea was to beta test 1.0 - getting new users
through the tutorial and some 0.96 users to port their apps to 1.0.
Overall we didn't find any serious bugs although porting is going to
be painful...
Ma
On Tue, Aug 19, 2008 at 4:16 PM, daonb <[EMAIL PROTECTED]> wrote:
> I could start a whole discussion as to what I learned about users out
> there and share some ideas on how to improve the tutorial so it will
> be easier for newcomers. But I know that django-developers is not the
> place for this.
Hi,
The `FileSystemStorage._save()` method seems to implicitly close the
uploaded file after it's been saved, preventing the following from
working:
storage.save('/images/image.gif', uploaded_image) # Store the original
thumbnail = Image.open(uploaded_image) # Doesn't work because
uploaded_image
Hi folks --
The docs refactor work is pretty much done; now I need a bunch more
eyes to look things over. There's still a bunch of TODOs (see below),
but it's better than the current docs and maintaining branched docs is
a major pain, so I plan to have this merged into trunk this week.
The best
Thanks very much for the pointer, Ramiro. It was indeed changes to
the "extra_select" QS param that caused Oracle problems, and I've
taken a similar approach to yours in fixing it.
Rather than flag "row_number()" as an extra_select parameter (and then
try to clean up after it later), Oracle now
Hi folks --
With Django 1.0 fast approaching, we need to get a few longish
documents written before 1.0: a set of release notes, and a detailed
porting guide covering all the changes up to 1.0.
Typically James or one of the committers writes these, but we're all
crazy swamped, so we need some he
On Sat, Aug 16, 2008 at 12:01 PM, Mike Scott <[EMAIL PROTECTED]> wrote:
> I'm -1. the permissions stuff is part of the auth app. It should dilute the
> models stuff. I'm sure theres a way using the generic relationship stuff to
> do a reverse relationship variable on whatever models you wish. But
I've been trying to stay up to date when testing locally and just
noticed 8399 seems to be the source of a break in my code where
MultiValueDict's iteritems was used. I see that this relates to
http://code.djangoproject.com/ticket/7331 and I understand a decision
had to be made.
iteritems used t
I'll take the porting guide - ticket #8438. Although I'm not going to
be in Portland, I'll do my best to have a draft ready by the weekend.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
Jacob Kaplan-Moss wrote:
> I've also put a built version of the docs online at
> http://docs.djangoproject.com/dev/. There are some problems with the
> version online right now; no need for bug reports since I'll be
> changing the online version to better fit into the django site over
> the next f
I attached a patch to #8160 that fixes this issue (and probably #8071).
I'm not sure what parts of BaseModelFormSet are considered official
API. In the patch ModelForm.save() is now called by
ModelFormSet.save(), and I think the methods save_new, save_existing,
save_existing_objects, and save_new
27 matches
Mail list logo
