Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #82407
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Subject | Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition |
| Date | 2014-12-11 21:48 -0500 |
| References | <CAPTjJmro9QQG43Fp+dXsNHaExFAbO4Tdg3d2u-3jiA3suRy6ew@mail.gmail.com> <1418249069475.965a6c@Nodemailer> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.16887.1418352538.18130.python-list@python.org> (permalink) |
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
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition Terry Reedy <tjreedy@udel.edu> - 2014-12-11 21:48 -0500
csiph-web