A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-May/134570.html below:

[Python-Dev] Where is our official policy of what platforms we do support?

[Python-Dev] Where is our official policy of what platforms we do support? [Python-Dev] Where is our official policy of what platforms we do support?Brett Cannon bcannon at gmail.com
Wed May 14 16:20:26 CEST 2014
Over the past week or so there have been 2 patches to add support for
various UNIX OSs. Now I thought we had stopped trying to add new esoteric
OSs (e.g. I had never heard of MirOS until the patch for it came in), but I
can't find a PEP that spells out what it takes to get a platform supported (
http://legacy.python.org/dev/peps/pep-0011/ is about removing platforms,
not keeping them or adding them unless you are re-adding one which
apparently just takes a volunteer).

Do we want an official policy written down in a PEP (yes, I can write it)?
Should I keep closing these patches and saying that we are not adding
support for new operating systems and be hand-wavy about it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140514/219be54c/attachment.html>
More information about the Python-Dev mailing list

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