Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Antonio Cavallo
> It almost always comes down to bytes vs. strings, IME. Cool, next time I have to port an extension written in C/C++ I'll be looking only for bytes vs. strings problems. I knew it was easy. Thanks ___ Python-Dev mailing list Python-Dev@python.o

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Apr 08, 2013, at 05:08 PM, Tres Seaver wrote: >FWIW, the effort of porting the "modern" bits of the Zope ecosystem (the >ones I still use in Pyramid apps today, meaning the component >architecture, the ZODB, and a few others) soaked up basically

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/08/2013 04:40 PM, Skip Montanaro wrote: > I'm really amazed at how many people seem to have the impression that > porting to Python 3 should be no big deal. FWIW, the effort of porting the "modern" bits of the Zope ecosystem (the ones I still

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Skip Montanaro
> If from the start you use: > - six ... There's the rub. We are not blessed with Guido's time machine where I work. Much of the Python code we run was written long before six was a gleam in anybody's eye. Heck, some of it was probably written before some active members of python-dev graduated

[Python-Dev] Python accepted as a GSoC 2013 mentoring organization!

2013-04-08 Thread Terri Oda
Congratulations all; we've been accepted as a mentoring organization for Google Summer of Code 2013! Students can check out our ideas page here: http://wiki.python.org/moin/SummerOfCode/2013 If you're interested in mentoring with the PSF and aren't already on the 2013 mentors mailing list, p

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Matthias Klose
Am 07.04.2013 20:02, schrieb Guido van Rossum: > But perhaps we could change the focus for 2.7 development a bit: > instead of fixing bugs (or bickering about whether something is a bug > fix or a new feature) we could limit changes to ensuring that it works > on newer platforms. Martin mentioned t

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Giampaolo Rodolà
2013/4/8 Stephen Hansen : > On Sun, Apr 7, 2013 at 6:53 AM, Christian Tismer > wrote: >> >> On 07.04.13 14:10, Skip Montanaro wrote: >> >> Where I work (a trading firm that uses Python as just one of many >> different pieces of technology, not a company where Python is the core >> technology upon

[Python-Dev] Fwd: SourceForge Project Upgrade Notification

2013-04-08 Thread Skip Montanaro
Obviously SourceForge doesn't think the current release interval is short enough. (Emphasis mine.) :-) Skip -- Forwarded message -- From: SourceForge.net Date: Mon, Apr 8, 2013 at 1:09 PM Subject: SourceForge Project Upgrade Notification To: nore...@in.sf.net Dear SourceForge

Re: [Python-Dev] [Python-checkins] cpython (3.3): Process DEFAULT values in mock side_effect that returns iterator.

2013-04-08 Thread Antoine Pitrou
On Mon, 8 Apr 2013 10:52:30 +0100 Michael Foord wrote: > On 7 April 2013 14:44, andrew.svetlov wrote: > > > http://hg.python.org/cpython/rev/18fd64f1de2d > > changeset: 83179:18fd64f1de2d > > branch: 3.3 > > user:Andrew Svetlov > > date:Sun Apr 07 16:42:24 2013 +0300 > >

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Mark Lawrence
On 08/04/2013 16:42, Stephen Hansen wrote: The thing is, 2.7 works. Some third-party libraries we rely upon have no clear sign for when they will be ported (such as wxPython), and though we are transitioning away from certain others (omniORB for Apache Thrift for example), that process itself is

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Stephen Hansen
On Sun, Apr 7, 2013 at 6:53 AM, Christian Tismer wrote: > On 07.04.13 14:10, Skip Montanaro wrote: > > Where I work (a trading firm that uses Python as just one of many > different pieces of technology, not a company where Python is the core > technology upon which the firm is based) we are only

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Brett Cannon
On Sat, Apr 6, 2013 at 5:02 PM, Benjamin Peterson wrote: > Per my last message, 2.7.4 has at long last been released. I apologize > for the long interval between 2.7.3 and 2.7.4. To create more > determinism in the future, I will be soon updating PEP 373 with > approximate dates of future 2.7 bugf

Re: [Python-Dev] [Python-checkins] cpython (3.3): Process DEFAULT values in mock side_effect that returns iterator.

2013-04-08 Thread Michael Foord
On 7 April 2013 14:44, andrew.svetlov wrote: > http://hg.python.org/cpython/rev/18fd64f1de2d > changeset: 83179:18fd64f1de2d > branch: 3.3 > user:Andrew Svetlov > date:Sun Apr 07 16:42:24 2013 +0300 > summary: > Process DEFAULT values in mock side_effect that returns ite

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Ned Deily
In article , Guido van Rossum wrote: [...] > But perhaps we could change the focus for 2.7 development a bit: > instead of fixing bugs (or bickering about whether something is a bug > fix or a new feature) we could limit changes to ensuring that it works > on newer platforms. Martin mentioned th

Re: [Python-Dev] The end of 2.7

2013-04-08 Thread Terry Jan Reedy
On 4/7/2013 2:02 PM, Guido van Rossum wrote: There's not much of a point in fixing bugs that always existed in 2.7, I has been suggested that backporting bugfix patches from current 3.x to 2.7 will make it easier to port from the atest 2.7.x to 3.x. I have no idea how true that is. since