On Thu, 2007-03-08 at 11:49 -0500, Joseph Perla wrote:
> Thanks for that thoughtful response. Let me just point to the
> specific one I've been hoping to get through for the past couple
> months, very small in scope and complete, that should be checked in:
> http://code.djangoproject.com/ticket/3
On Thu, 2007-03-08 at 11:08 -0600, Jeremy Dunck wrote:
> On 3/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > A bunch of them have subsequently been notated as waiting until after
> > 0.96 or they are for another branch. Some others are not no-brainers, so
> > require some thought and for
Jeremy Dunck schrieb:
> On 3/8/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>> Jeremy Dunck:
>>> I wonder if, due to patches getting out of sync with trunk, tickets
>>> that have been "Ready for Checkin" for longer than x weeks should go
>>> back to Accepted?
>> Why? As long as they apply, wha
On 3/8/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Jeremy Dunck:
> > I wonder if, due to patches getting out of sync with trunk, tickets
> > that have been "Ready for Checkin" for longer than x weeks should go
> > back to Accepted?
>
> Why? As long as they apply, what's the problem?
Right-
Jeremy Dunck:
> I wonder if, due to patches getting out of sync with trunk, tickets
> that have been "Ready for Checkin" for longer than x weeks should go
> back to Accepted?
Why? As long as they apply, what's the problem?
Michael
--~--~-~--~~~---~--~~
You recei
On 3/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> A bunch of them have subsequently been notated as waiting until after
> 0.96 or they are for another branch. Some others are not no-brainers, so
> require some thought and for a committer to have a block of time
> available to drop them in
Thanks for that thoughtful response. Let me just point to the specific one
I've been hoping to get through for the past couple months, very small in
scope and complete, that should be checked in:
http://code.djangoproject.com/ticket/3182 . I assumed that since this
simple one hasn't gone through,
On Mar 2, 11:31 am, "Rubic" <[EMAIL PROTECTED]> wrote:
> One possibility would be to allow max_length to be
> used as a maxlength attribute so applications could
> begin to future-proof.
The patch for this is waiting for checkin (minus Honza's suggestion of
a depreciation note)
http://code.django
On Tue, 2007-03-06 at 17:39 -0500, Joseph Perla wrote:
> They don't need to be in 0.96, but can someone at least check in the
> tickets already decided as ready for check-in?
> http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&stage=Ready+for+checkin
> Some of these h
They don't need to be in 0.96, but can someone at least check in the tickets
already decided as ready for check-in?
http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&stage=Ready+for+checkin
Some of these have been complete and ready for 2 months.
j
On 3/6/07, Simon G.
#3625 ( http://code.djangoproject.com/ticket/3625 ) looks like a good
candidate - it's a Python 2.3 issue with rsplit in the test system.
It's been reported three times, so people are definitely running into
it.
3625 has a simple patch to fix this.
--Simon
--~--~-~--~~~
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
+1 for me too
On 2 mar, 05:33, "olive" <[EMAIL PROTECTED]> wrote:
> +1 for me
>
> On Mar 1, 5:19 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
>
> > On 3/1/07, David Larlet <[EMAIL PROTECTED]> wrote:
>
> > > What about bug #2282? What's the actual status? A patch is proposed,
> > > it doesn't su
+1 for me
On Mar 1, 5:19 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 3/1/07, David Larlet <[EMAIL PROTECTED]> wrote:
>
> > What about bug #2282? What's the actual status? A patch is proposed,
> > it doesn't suit any case but it's a good start for a part of the
> > world.
>
> It still need
On 3/1/07, Rubic <[EMAIL PROTECTED]> wrote:
>
> On Mar 1, 3:12 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > AFAIK it will be migrated eventually to being 'max_length' everywhere,
> > but probably not for this release because that's a
> > backwards-incompatible change.
>
> One possibility woul
On Mar 1, 3:12 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> AFAIK it will be migrated eventually to being 'max_length' everywhere,
> but probably not for this release because that's a
> backwards-incompatible change.
One possibility would be to allow max_length to be
used as a maxlength attri
On 3/1/07, Kai Kuehne <[EMAIL PROTECTED]> wrote:
> Could you decide on whether to name the attribute maxlength or max_length?
> Well... it's not *that* important but it this is ugly, imho.
AFAIK it will be migrated eventually to being 'max_length' everywhere,
but probably not for this release bec
Could you decide on whether to name the attribute maxlength or max_length?
Well... it's not *that* important but it this is ugly, imho.
http://code.djangoproject.com/ticket/3622
Greetings
Kai
PS: I like the mood here, thanks to everybody. :)
--~--~-~--~~~---~--~
On 3/1/07, David Larlet <[EMAIL PROTECTED]> wrote:
> What about bug #2282? What's the actual status? A patch is proposed,
> it doesn't suit any case but it's a good start for a part of the
> world.
It still needs a discussion and decision about how far we want to go
to support (essentially) arbit
> > 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
>
What about bug #2282? What's the actual status? A patch is proposed,
it doesn't suit any case but it's a good start for a part of the
world.
Chee
> 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
There one tiny bugfix in [3501] regarding the _sqlite_extract function
that i'd like to see committed. It breaks the admin date_hierarchy
filter for mod
On Feb 27, 10:41 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> I tried it, and it worked for me. Can you provide an example where it fails?
I updated the trunk and it works perfectly.
It was obviously my fault.
Thank you very much.
Massimiliano
--~--~-~--~~~---
On Mon, Feb 26, 2007 at 06:16:31PM -, [EMAIL PROTECTED] wrote:
>
> I would like to see http://code.djangoproject.com/ticket/3297
> implemented before 0.96 if possible.
I definitely agree. And more It's a working one!
I think that newforms are the true change in this releise. We need to try
On 27 Feb, 10:41, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> I tried it, and it worked for me.
> Can you provide an example where it fails?
I'll give it a deeper look tomorrow. I'll let you know.
Thank you very much
Massimiliano
--~--~-~--~~~---~--~~
Y
On 2/27/07, Massimiliano Ravelli <[EMAIL PROTECTED]> wrote:
>
> On 26 Feb, 13:31, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> > #3253 has a working patch with documentation. I've closed yours as
> > duplicate of #3253.
>
> Hi Micheal, Hi Russ
>
> >From ticket #3253:
> "I didn't check whether it
On 26 Feb, 13:31, Michael Radziej <[EMAIL PROTECTED]> wrote:
> #3253 has a working patch with documentation. I've closed yours as
> duplicate of #3253.
Hi Micheal, Hi Russ
>From ticket #3253:
"I didn't check whether it actually works for manage.py test";
I made a quick test and it seems that i
I would like to see http://code.djangoproject.com/ticket/3297
implemented before 0.96 if possible.
On 26 Feb, 19:09, "Rob Hudson" <[EMAIL PROTECTED]> wrote:
> On Feb 26, 9:46 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
> wrote:
>
> > I've close #760 and #3335 with this comment:
>
> Design decisio
On Feb 26, 9:46 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> I've close #760 and #3335 with this comment:
Design decision: Django won't include default 404 and 500 templates.
OK.
But does that invalidate those bugs? The default templates were a
possible solution to fix both of them.
Bo
On 2/26/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
> Could we get a design decision on whether to add default, non-django
> looking 404 and 500 templates?
I've close #760 and #3335 with this comment:
"""
Django's not going to ever include a default 404 or 500 template. If
we do, people won't be
Could we get a design decision on whether to add default, non-django
looking 404 and 500 templates?
It seems pretty minor but important as there are 2 cases where
switching from DEBUG=True in development to DEBUG=False for production
could end up biting you...
1) With DEBUG=False and a 500 occur
On 2/26/07, Espen Grindhaug <[EMAIL PROTECTED]> wrote:
> I got a little suggestion, and I think a lot of people agrees with me:
> how about trying to merge one or two of the 100 development branches
> into trunk.
We can only merge a branch when it's done, and unfortunately there
aren't many branc
I got a little suggestion, and I think a lot of people agrees with me:
how about trying to merge one or two of the 100 development branches
into trunk.
Anyhow once again thanks a lot for a great framework.
Espen
--~--~-~--~~~---~--~~
You received this message bec
On Mon, Feb 26, 2007 at 12:04:29AM -0600, Jacob Kaplan-Moss wrote:
>
> On 2/25/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> > http://code.djangoproject.com/ticket/3440 , Models.__init__
> > refactoring.
>
> #3440 is fixed and has to do with DateQuerySet; did you mean #3438?
Pardon, 3438 is the
Russell Keith-Magee:
> Oops :-). To make up for my boo boo, please accept [4608]
Merci! Anyways, duplicates are unavoidable in the Django ticket djungle ;-)
Michael
--
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel +49-911-9352-0 - Fax +49-911-9352-100
http://www.noris
On 2/26/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> > I think that a different exit code when one or more tests fail would
> > really
> > be helpful in case of automated tests.
>
> http://code.djangoproject.com/ticket/3253
>
> ;-)
Oops :-). To make up for my boo boo, please accept [4608]
Russell Keith-Magee:
> Nice idea, and shouldn't be too much effort. I've logged the idea as
> #3576 to make sure it doesn't get lost; I should get a chance to look
> at it over the next few days.
#3253 has a working patch with documentation. I've closed yours as
duplicate of #3253.
Michael
--
Massimiliano Ravelli:
> Hi Russ,
> I'm using your latest patch (ticket #2333) in my applications:
> I find it useful and extremely fast !
>
> I configured the svn repository of my django apps to work with
> buildbot and
> have all tests done each time a commit is performed.
>
> Buildbot runs "py
On 2/26/07, Massimiliano Ravelli <[EMAIL PROTECTED]> wrote:
>
> Hi Russ,
> I'm using your latest patch (ticket #2333) in my applications:
> I find it useful and extremely fast !
Glad you like it.
> I think that a different exit code when one or more tests fail would
> really
> be helpful in case
Hi Russ,
I'm using your latest patch (ticket #2333) in my applications:
I find it useful and extremely fast !
I configured the svn repository of my django apps to work with
buildbot and
have all tests done each time a commit is performed.
Buildbot runs "python manage.py test" but shows the green
On 26 Feb, 04:56, "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.
Because you did ask, the one that's annoying me most at the moment
(and preventing me
On 2/26/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 2/26/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> > AFAIK, it is finished, just waiting for Adrian's ok. Is there
> > something missing that I'm not aware of?
>
> Oh, I thought there was something missing *I* wasn't aware of :
On 2/26/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 2/25/07, Rubic <[EMAIL PROTECTED]> wrote:
> > In keeping with the overall theme of testing at this
> > year's PyCon, it would be nice to have integrated
> > testing (fixtures, ticket #2333) brought to resolution.
>
> I really, really,
On 2/26/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> AFAIK, it is finished, just waiting for Adrian's ok. Is there
> something missing that I'm not aware of?
Oh, I thought there was something missing *I* wasn't aware of :)
Please go ahead and check it in! I'll focus on writing docs (and
On 2/25/07, Rubic <[EMAIL PROTECTED]> wrote:
> In keeping with the overall theme of testing at this
> year's PyCon, it would be nice to have integrated
> testing (fixtures, ticket #2333) brought to resolution.
I really, really, *really* agree, and I'm going to look at seeing if I
can channel Russ
On 2/25/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> http://code.djangoproject.com/ticket/3440 , Models.__init__
> refactoring.
#3440 is fixed and has to do with DateQuerySet; did you mean #3438?
Jacob
--~--~-~--~~~---~--~~
You received this message because you
On 2/25/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> One thing comes to my mind, supporting non-ASCII characters in newforms:
Since newforms will still be "new" in 0.96, I'm could take or leave
these before it. I'll try to get to 'em, though.
> http://code.djangoproject.com/wiki/FeatureGrou
In keeping with the overall theme of testing at this
year's PyCon, it would be nice to have integrated
testing (fixtures, ticket #2333) brought to resolution.
It was great to briefly meet everyone over the past
few days in Dallas.
--
Jeff Bauer
Rubicon, Inc.
--~--~-~--~~---
On Sun, Feb 25, 2007 at 10:56:36PM -0600, James Bennett 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.
http://code.djangoproject.com/ticket/3440 , Models.__init__
refactoring.
Fair amou
Hi James,
James Bennett 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 but code, so hopeful
Upcoming Django release, and the future
As we sit here in warm, sunny Dallas, meditating on how next year's
PyCon will be in cold, cloudy Chicago, we're also getting ready to
push out a new release of Django, and with that there are some things
you all need to know, and as you
50 matches
Mail list logo
