brettcannon

12 ms·

61.
by brettcannon 11y ago
Sure, there's a chance people will pick up the mantle and essentially fork Python 2.7 to do unofficial bugfix releases past 2020; as you pointed out, it's open source and people can do what they want. But my point is there is no g
62.
by brettcannon 11y ago
See http://www.snarky.ca/why-print-became-a-function-in-python-3 for the reasoning behind making `print` a function.
63.
by brettcannon 11y ago
Pyston targets Python 2.7 because that's what they use on their servers. As for why Pyston over PyPy, http://blog.pyston.org/2015/11/24/pyston-talk-recording/ has a nice video that mentions why (amo
64.
by brettcannon 11y ago
Technically the goal was a majority of new projects started using Python 3 in 5 years. Regardless, everyone knew it would take several years to reach a point like this.
65.
by brettcannon 11y ago
There's actually been a lot of work the past few months to speed up CPython 3.6. I expect there will be more news coming out of PyCon US on stuff related to this.
66.
by brettcannon 11y ago
Their PyPI page explicitly says otherwise: https://pypi.python.org/pypi/supervisor . It looks like there is support in their repository but not in any official release (yet).
67.
by brettcannon 11y ago
pyreadiness.org uses https://github.com/brettcannon/caniusepython3 to figure out if a project supported Python 3. The issue is that gevent doesn't specify their support through a trove classifier on PyPI. There is
68.
by brettcannon 11y ago
The Python development team will cease supporting Python 2.7 in 2020. After that you will have to buy support from someone like Red Hat or Continuum Analytics.
69.
Python 3 Is Winning Library Developer Support(blogs.msdn.microsoft.com)
297 points by brettcannon 11y ago|185 comments
70.
by brettcannon 11y ago
There are no plans to break backwards-compatibility in Python 4 like Python 3 did with Python 2. If there is any breaking change it will be something like the C API to remove the GIL or something (otherwise it will be standard stuff like re
71.
by brettcannon 11y ago
See https://docs.python.org/3/howto/pyporting.html for the most modern approach to porting Python 2 code to Python 2/3 code.
72.
by brettcannon 11y ago
Armin handed over development and now Modernize is actively developed at https://github.com/python-modernize/python-modernize
73.
by brettcannon 11y ago
Welcome! Glad you liked it.
74.
by brettcannon 11y ago
The way the standard library is managed in terms of new things is it needs to be proved in the community for a year or more before we consider adding it. Since async is so new it's a bit early to get be changing things until we see how
75.
by brettcannon 11y ago
C# a actually inspired Python's implementation. Python historically takes ideas from other languages and refines them to Python's style.
76.
How async/await works in Python 3.5(snarky.ca)
63 points by brettcannon 11y ago|10 comments
77.
by brettcannon 11y ago
Thanks to all of the great questions we got, we have now written an FAQ for the project: https://github.com/Microsoft/Pyjion#faq
78.
by brettcannon 11y ago
It's too early. We want to prove to ourselves that we can get the performance we want before proposing the changes we think we want to CPython's C API.
79.
by brettcannon 11y ago
What ericfrederich said is all accurate. We are also considering playing with ChakraCore as a JIT back-end as well once we are sure that our abstract interpreter code that drives the JIT emission code is compatible with Python semantics.
80.
by brettcannon 11y ago
Trent already replied about PyParallels (and yes, we are aware of his work). We are also aware of Pyston. There might be a chance that they could end up using our JIT hooks, but they also started a full year before us so they are not curren
81.
by brettcannon 11y ago
You can vote for that feature at https://excel.uservoice.com/forums/304921-excel-for-windows-...
82.
by brettcannon 11y ago
Yes. :) It's exploratory in the sense that we are seeing if this general approach works for CPython. But if this exploratory work shows promise, then we will see it through. And since I'm also a member of the Python development te
83.
by brettcannon 11y ago
One thing to note about the list of failing tests is the vast majority of them are due to a single bug (or two): https://github.com/Microsoft/Pyjion/issues/103 . And we currently only have 11 open bugs so the
84.
by brettcannon 11y ago
Exactly, we started on Windows out of ease-of-start/momentum. There are absolutely no plans to make this a Windows-exclusive. Basically we want to show this work pans out before working before putting in the work to make it cross-platf