Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #97291 > unrolled thread
| Started by | Chris Warrick <kwpolska@gmail.com> |
|---|---|
| First post | 2015-10-01 19:16 +0200 |
| Last post | 2015-10-01 19:16 +0200 |
| 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.
Re: The Nikola project is deprecating Python 2.7 (+2.x/3.x user survey results) Chris Warrick <kwpolska@gmail.com> - 2015-10-01 19:16 +0200
| From | Chris Warrick <kwpolska@gmail.com> |
|---|---|
| Date | 2015-10-01 19:16 +0200 |
| Subject | Re: The Nikola project is deprecating Python 2.7 (+2.x/3.x user survey results) |
| Message-ID | <mailman.303.1443719813.28679.python-list@python.org> |
On 1 October 2015 at 18:43, <paul.hermeneutic@gmail.com> wrote: > Python 3 has venv in the kit. Is there a reason users should get the > virtualenv add-on? Both can be used; I wrote about virtualenv because it’s the tried-and-true solution (and is it guaranteed in all Linux distros anyway?) On 1 October 2015 at 19:02, Stefan Behnel <stefan_ml@behnel.de> wrote: > Chris Warrick schrieb am 01.10.2015 um 18:26: >> The Nikola developers decided to deprecate Python 2.7 support. > > I wonder why it took the Nikola project so long to take that decision. > Python 3.3 came out almost exactly three(!) years ago and seems to have all > major features that they would require. Nikola's PyPI page claims support > of Python 3.3 for just about as long, since version 5.4 or so, which means > that all of their dependencies were already available back then. > > It's a different thing for *libraries* that Python 2.x users still depend > on, but for an *application* that has all its (necessary) dependencies > available in Python 3.x, I can't see a general reason to keep supporting > both language versions. > > Stefan We did it now because it all started with frustration with 2.7 [0]. Also, doing it back in 2012/2013 would be problematic, because back then not all Linux distros had an easily installable Python 3 stack (and RHEL 7 still doesn’t have one in the default repos) [0]: http://ralsina.me/weblog/posts/floss-decision-making-in-action.html -- Chris Warrick <https://chriswarrick.com/> PGP: 5EAAEA16
Back to top | Article view | comp.lang.python
csiph-web