Re: Sprint in San Francisco

2011-12-03 Thread Jeremy Dunck
On Sat, Dec 3, 2011 at 1:27 PM, Brodie Rao wrote: > Bitbucket/Atlassian would love to host a sprint. We're about to move > from the Mission to our own office building in SoMa in a couple of > weeks. We'll have plenty of space for anyone who wants to attend. Thanks for the offer, Brodie. I'll wri

Re: Sprint in San Francisco

2011-12-03 Thread Jeremy Dunck
On Sat, Dec 3, 2011 at 7:59 PM, Russell Keith-Magee wrote: > On Saturday, December 3, 2011, Jeremy Dunck wrote: >> Hey all, >>  With the 1.4 release coming up, I thought it'd be a good time to >> schedule a sprint to get in any ponies or help shake out bugs. > > Sounds like a great idea to me! >

Sprint in San Francisco

2011-12-03 Thread Russell Keith-Magee
On Saturday, December 3, 2011, Jeremy Dunck wrote: > Hey all, > With the 1.4 release coming up, I thought it'd be a good time to > schedule a sprint to get in any ponies or help shake out bugs. Sounds like a great idea to me! Since you're the DSF secretary, you already know that the DSF will he

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

2011-12-03 Thread Vinay Sajip
On Dec 3, 8:50 pm, Karen Tracey wrote: > What about Pythons 2.5 and 2.6? Okay, I've now done some more testing, and with some minor changes, I can report that good results were obtained on Pythons 2.5.4 and 2.6.2. The remaining failures are representational ones - u'foo' vs. 'foo' and order of d

Django-nonrel patches

2011-12-03 Thread Jonas H.
Hello list! On Jacob's suggestion in this thread [1] back in April, I split the diff between Django trunk and Django-nonrel into logically separated patches. I uploaded most of them to the ticket tracker (a few things are still missing but these are the most important changes): https://code

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

2011-12-03 Thread Vinay Sajip
On Dec 3, 8:50 pm, Karen Tracey wrote: > What about Pythons 2.5 and 2.6? I did a bit more checking, and a bit more work will be required on 2.5 and 2.6: for example, on 2.5, parse_qsl needs to come from elsewhere, and on 2.6, unittest.skipIf needs to come from somewhere else. So some changes n

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

2011-12-03 Thread Vinay Sajip
On Dec 3, 8:50 pm, Karen Tracey wrote: > On Fri, Dec 2, 2011 at 10:55 AM, Vinay Sajip wrote: > > > The Python 3 port now has all tests passing on 2.7.2 and 3.2.2 with > > the same codebase: > > What about Pythons 2.5 and 2.6? I've done nothing intentionally that prevents the port from working on

Re: Sprint in San Francisco

2011-12-03 Thread Brodie Rao
On Fri, Dec 2, 2011 at 2:01 PM, Jeremy Dunck wrote: > Hey all, >  With the 1.4 release coming up, I thought it'd be a good time to > schedule a sprint to get in any ponies or help shake out bugs. > >  I'm in San Francisco these days, which I hear is an OK place to try > to host a sprint.  Given th

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

2011-12-03 Thread Luke Plant
To follow up some discussion on reddit, the subject of exceptions was brought up. The Python 2.X/3.X compatible way to do exceptions requires: e = sys.exc_info()[1] ...if you need the actual exception object. As discussed on reddit, this is slow on PyPy. I did some checks in the py3k patch of

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

2011-12-03 Thread Karen Tracey
On Fri, Dec 2, 2011 at 10:55 AM, Vinay Sajip wrote: > The Python 3 port now has all tests passing on 2.7.2 and 3.2.2 with > the same codebase: > What about Pythons 2.5 and 2.6? Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To pos

Re: Deprecate change pk + save behavior for 1.4

2011-12-03 Thread Anssi Kääriäinen
On Dec 3, 7:18 pm, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/03/2011 02:13 AM, Anssi K ri inen wrote: > > > Admin should be fixed [#2259]. Making PK fields non-editable in > > ModelForms would be good, too. Is it OK to consider the current > > ModelForm behavior

Re: Deprecate change pk + save behavior for 1.4

2011-12-03 Thread Carl Meyer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/03/2011 02:13 AM, Anssi Kääriäinen wrote: > Admin should be fixed [#2259]. Making PK fields non-editable in > ModelForms would be good, too. Is it OK to consider the current > ModelForm behavior a bug, or will it need a deprecation cycle? I thin

Re: Deprecate change pk + save behavior for 1.4

2011-12-03 Thread Carl Meyer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/03/2011 10:18 AM, Carl Meyer wrote: > So what about admin users who are currently relying on this behavior as > a way to clone objects with natural PKs (given that the > save-and-add-another button is useless with natural PKs unless you can > exp

Re: Deprecate change pk + save behavior for 1.4

2011-12-03 Thread Anssi Kääriäinen
On Dec 3, 5:03 am, Carl Meyer wrote: > Did we gain support for multi-column PK recently and I missed it? Or is > this just a hypothetical example assuming such support is added in the > future? Yes, this is a hypothetical example, inspired by the GSoC work on multicolumn primary keys [https://git