Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140107/0ef93b10/attachment.html below:
<p dir="ltr"><br>
On 7 Jan 2014 08:03, "Antoine Pitrou" <<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>> wrote:<br>
><br>
> On Tue, 7 Jan 2014 09:16:10 +1000<br>
> Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br>
> > For anyone that isn't already aware, I wrote a Q & A about Python 3 last<br>
> > year (in response to an article about how we should have fixed the GIL<br>
> > instead of Unicode), and I've updated it extensively over the past several<br>
> > days due to Alex's misunderstanding of the objectives for Python 3.4 as<br>
> > well as Armin's latest piece on the increased difficulties in writing wire<br>
> > protocol handling code.<br>
><br>
> A couple remarks:<br>
><br>
> - the unicode section would gain being a little more on the practical<br>
> side; for example the "surrogateescape" paragraph is an obscure and<br>
> theoretical way of saying unicode filepaths (etc.) are fully<br>
> supported on all platforms<br>
><br>
> - also, it doesn't seem very clear that the primary string type (str)<br>
> is now unicode; this has important consequences, for example<br>
> non-ASCII exception messages work fine in 3.x while they were very<br>
> delicate to work with in 2.x<br>
><br>
> - when discussing Twisted / gevent alternatives, you should also mention<br>
> Tornado, which is especially interesting because it works on both<br>
> Python 2 and Python 3, and therefore presents a nice migration path</p>
<p dir="ltr">Thanks, I've addressed these and a couple of other points people brought up (e.g. it is cx-freeze that supports Py3k, not py2exe).</p>
<p dir="ltr">> - perhaps you should discuss the idea that "uptake is slow", because<br>
> the numbers are rather conflicting on that point; see what I wrote in<br>
> <a href="https://mail.python.org/pipermail/python-list/2014-January/663922.html">https://mail.python.org/pipermail/python-list/2014-January/663922.html</a><br>
> and also Chris Angelico's elaboration in<br>
> <a href="https://mail.python.org/pipermail/python-list/2014-January/664003.html">https://mail.python.org/pipermail/python-list/2014-January/664003.html</a></p>
<p dir="ltr">I haven't incorporated these observations yet, but I will. It ties in closely with the point that bootstrapping the new Python 3 application ecosystem with cross-version libraries and frameworks is not the same thing as migrating the existing Python 2 *application* ecosystem, and the latter is expected to take *much* longer (since existing Python 2 users will have, of necessity, already worked around or avoided the bugs and limitations of that version of the language).</p>
<p dir="ltr">Cheers,<br>
Nick.</p>
<p dir="ltr">><br>
> Regards<br>
><br>
> Antoine.<br>
><br>
><br>
> _______________________________________________<br>
> Python-Dev mailing list<br>
> <a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
> <a href="https://mail.python.org/mailman/listinfo/python-dev">https://mail.python.org/mailman/listinfo/python-dev</a><br>
> Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com">https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com</a><br>
</p>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4