On 2/25/07, James Bennett <[EMAIL PROTECTED]> wrote:
If there's a bug that's been annoying the heck out of you and you want
> it fixed before the release, this would be the time to speak up about
> it. We have a fairly high concentration of Django developers all in
> one place with nothing to do
On Tuesday, February 27, 2007, 8:41:44 AM, Marc Fargas Esteve wrote:
> Hi Andrew,
> There's a ticket for that openned:
> http://code.djangoproject.com/ticket/3589
> And it's closed as fixed :)
Thanks! The ticket itself doesn't have 'postgresql_psycopg2' in it,
so I didn't find it searching. An
Hi Andrew,
There's a ticket for that openned: http://code.djangoproject.com/ticket/3589
And it's closed as fixed :)
On 2/27/07, Andrew Diederich <[EMAIL PROTECTED]> wrote:
>
> On Monday, February 26, 2007, 4:39:29 PM, James Bennett wrote:
>
> > On 2/26/07, Andrew Diederich <[EMAIL PROTECTED]> wro
On Monday, February 26, 2007, 4:39:29 PM, James Bennett wrote:
> On 2/26/07, Andrew Diederich <[EMAIL PROTECTED]> wrote:
>> On Monday, February 26, 2007, 3:00:30 PM, Jacob Kaplan-Moss wrote:
>> > For the other bit, though, see [4624].
>>
>> This ticket doesn't exist. I looked for similarly number
On 26/02/07, James Bennett <[EMAIL PROTECTED]> wrote:
> If there's a bug that's been annoying the heck out of you and you want
> it fixed before the release, this would be the time to speak up about
> it. We have a fairly high concentration of Django developers all in
> one place with nothing to d
On Montag, 26. Februar 2007, James Bennett wrote:
Hi James,
[...]
> If there's a bug that's been annoying the heck out of you and you want
> it fixed before the release, this would be the time to speak up about
> it. We have a fairly high concentration of Django developers all in
> one place wit
On 2/27/07, David Larlet <[EMAIL PROTECTED]> wrote:
>
> 2007/2/27, Manoj Govindan <[EMAIL PROTECTED]>:
> >
> > Will 0.96 have support for fixtures (a la #2333)?
> > Also, am I the only one waiting for them? ;)
> >
>
> Read the entire thread, we are all waiting for a single word of Adrian ;-).
FY
2007/2/27, Manoj Govindan <[EMAIL PROTECTED]>:
>
> Will 0.96 have support for fixtures (a la #2333)?
> Also, am I the only one waiting for them? ;)
>
Read the entire thread, we are all waiting for a single word of Adrian ;-).
Cheers,
David Larlet
--~--~-~--~~~---~--
Will 0.96 have support for fixtures (a la #2333)?
Also, am I the only one waiting for them? ;)
Regards,
Manoj
On Feb 26, 9:56 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> Upcoming Django release, and the future
>
> As we sit here in warm, sunny Dallas, meditating on how next year's
> PyCon w
Malcolm said:
> I wasn't going to look at it unless I ran out of things to do. That
> hasn't happened yet. You may remember me saying I don't like edit
> inline, so developing enthusiasm to look at these bugs is difficult. We
> have to fix them somehow, so if somebody else wants to do that, I'm n
> If there's a bug that's been annoying the heck out of you and you want
> it fixed before the release, this would be the time to speak up about
> it. We have a fairly high concentration of Django developers all in
> one place with nothing to do but code, so hopefully we'll be able to
> hit a lot
> Can you create a ticket with this on it so I don't lose track of it?
http://code.djangoproject.com/ticket/3587
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
On 2/26/07, Chris Brand <[EMAIL PROTECTED]> wrote:
> Ok, I got hold of my code.
[snip]
Can you create a ticket with this on it so I don't lose track of it?
Reading through it all is a little difficult, so I'm gonna want to
have it somewhere I can refer back to.
Thanks!
Jacob
--~--~-~-
On 2/26/07, Andrew Diederich <[EMAIL PROTECTED]> wrote:
> I'd like to see the mssql patches applied, ticket
> http://code.djangoproject.com/ticket/2358. I'd also like to see the
> postgresql_psycopg2 database option mentioned in the default comments
> in the settings.py file for the DATABASE_ENGI
> > Please do elaborate on this. AFAIK FKs in filter() work just fine, so
> > if there's something broken we should know about it right away.
>
> I found ticket 2076, but that only concerns order_by().
>
> I haven't got access to my code at the moment.
Ok, I got hold of my code.
Of course (I h
On Sunday, February 25, 2007, 9:56:36 PM, James Bennett wrote:
> If you've got any questions about all of this, feel free to reply and
> I'll do my best to answer them or delegate to someone who can. And if
> you've got some free time this week and want to help us kill bugs in
> the run up to 0.9
> I'm not sure how Chris is filtering/ordering, but there are
> several ways of specifying fields, depending on the context. In
> filtering, one needs to use the double-underscore scheme as in
>
> Foo.objects.filter(foreignfieldname__foreignfield = 42)
>
> whereas in ordering, IIRC, you h
>> I've been using 0.95 for a few months now, and the one thing that is really
>> annoying is using foreign keys in filter() and order_by() statements. Not
>> sure about a bug # (I will see if I can find one), but I always seem to end
>> up with errors about unknown table names, and end up having
> Please do elaborate on this. AFAIK FKs in filter() work just fine, so
> if there's something broken we should know about it right away.
I found ticket 2076, but that only concerns order_by().
I haven't got access to my code at the moment.
Chris
--~--~-~--~~~---~
On 2/26/07, Chris Brand <[EMAIL PROTECTED]> wrote:
> I've been using 0.95 for a few months now, and the one thing that is really
> annoying is using foreign keys in filter() and order_by() statements. Not
> sure about a bug # (I will see if I can find one), but I always seem to end
> up with error
> If there's a bug that's been annoying the heck out of you and you want
> it fixed before the release, this would be the time to speak up about
> it. We have a fairly high concentration of Django developers all in
> one place with nothing to do but code, so hopefully we'll be able to
> hit a lot
> Did anyone ever figure out if we can (legally/morally) include
> decimal.py as django.utils.decimal (for 2.3 support)?
>
Given Malcolm's perspective, let me know if the design decision would be
to include decimal.py. If it is, I can try to do some leg work to track
down the legal aspects. Ju
On Sun, 2007-02-25 at 23:56 -0600, Jacob Kaplan-Moss wrote:
> On 2/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
[...]
> > Third, there are lots of translation tickets ready for checkin, which
> > would be nice to patch in. Django's got a good reputation for i18n/
> > l10n, so getting these
On Mon, 2007-02-26 at 00:00 -0600, Jacob Kaplan-Moss wrote:
> On 2/25/07, Chris Moffitt <[EMAIL PROTECTED]> wrote:
> > Also, I'd like to see some of the decimal related tickets worked on but
> > this may have to wait until 1.0.
> > http://code.djangoproject.com/wiki/VersionOneFeatures#DecimalField
On Sun, 2007-02-25 at 23:56 -0600, Jacob Kaplan-Moss wrote:
> On 2/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
[...]
> > Third, there are lots of translation tickets ready for checkin, which
> > would be nice to patch in. Django's got a good reputation for i18n/
> > l10n, so getting these
On 2/25/07, Chris Moffitt <[EMAIL PROTECTED]> wrote:
> Also, I'd like to see some of the decimal related tickets worked on but
> this may have to wait until 1.0.
> http://code.djangoproject.com/wiki/VersionOneFeatures#DecimalField
Did anyone ever figure out if we can (legally/morally) include
dec
On 2/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> My vote would be for spending some time on edit_inline (e.g.
> http://code.djangoproject.com/wiki/FeatureGrouping#Multipleedit_inlineissues),
> as this alone is causing craploads of bugs and cleaning all these out
> would be great. AFAIK,
On Sun, 2007-02-25 at 21:22 -0800, [EMAIL PROTECTED] wrote:
> Excellent, I hope you guys get many hours for coding!
>
> Here's a few comments based on my triage experience (whatever that's
> worth):
>
> My vote would be for spending some time on edit_inline (e.g.
> http://code.djangoproject.com/
> If there's a bug that's been annoying the heck out of you and you want
> it fixed before the release, this would be the time to speak up about
> it. We have a fairly high concentration of Django developers all in
> one place with nothing to do but code, so hopefully we'll be able to
> hit a lot
Excellent, I hope you guys get many hours for coding!
Here's a few comments based on my triage experience (whatever that's
worth):
My vote would be for spending some time on edit_inline (e.g.
http://code.djangoproject.com/wiki/FeatureGrouping#Multipleedit_inlineissues),
as this alone is causing
30 matches
Mail list logo
