On 31 August 2016 at 00:55, Gregory P. Smith <greg at krypto.org> wrote: > I find that users of such systems either use only what their distro itself > supplies (ie: ancient versions at that point) or are fully comfortable > building any dependencies their own software needs. If they are comfortable > building a CPython runtime in the first place, they should be comfortable > building required libraries. Nothing new there In our environment (corporate systems locked to older OS releases, with Python *not* a strategic solution but used for ad-hoc automation) it's quite common to find only an ancient version of Python available, but want to build a new version without any ability to influence corporate IT to allow new versions of the necessary libraries. But I strongly agree, this is *my* problem, and Python policy should not be based on the idea that what I want to do "should" be supported. So +1 on the proposed change here. Paul
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