Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #82407 > unrolled thread

Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition

Started byTerry Reedy <tjreedy@udel.edu>
First post2014-12-11 21:48 -0500
Last post2014-12-11 21:48 -0500
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition Terry Reedy <tjreedy@udel.edu> - 2014-12-11 21:48 -0500

#82407 — Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition

FromTerry Reedy <tjreedy@udel.edu>
Date2014-12-11 21:48 -0500
SubjectRe: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition
Message-ID<mailman.16887.1418352538.18130.python-list@python.org>
On 12/10/2014 5:04 PM, Bruno Cauet wrote:
> I hesitated a while before deciding not to include it! Apart from python
> core development what would be the reasons to work mostly on this version ?

where 'This version' == 3.5.  A possible reason: one is developing an 
app expected to be released fall 2015 after the 3.5 release and the app 
depends on something new in 3.5.  I must admit though that I cannot 
think of any such thing now for 3.5.  For 3.3 there was the new unicode, 
which was first committed about a year before release.  For 3.4, there 
was asyncio, but it was not committed until beta1, and was hardly usable 
then.

So it was a defensible position.  Anyone who would check 3.5 could just 
as well check 3.4 and have most of the same impact on the summary.

-- 
Terry Jan Reedy

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web