Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Victor Stinner
2017-11-07 0:41 GMT+01:00 Serhiy Storchaka : > Several month ago there was a couple of buildbots including NetBSD and > OpenBSD. What happened to them? Was the support of NetBSD and OpenBSD > officially stopped as well as the support of OpenIndiana? While I don't recall seeing any NetBSD buildbot,

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Serhiy Storchaka
06.11.17 19:41, Victor Stinner пише: Example of platforms: MinGW, Cygwin, OpenBSD, NetBSD, xWorks RTOS, etc. But the way, is there an exhaustive list of platforms "officially" supported by CPython? Several month ago there was a couple of buildbots including NetBSD and OpenBSD. What happened t

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Serhiy Storchaka
06.11.17 23:24, Antoine Pitrou пише: On Mon, 6 Nov 2017 18:41:30 +0100 Victor Stinner wrote: Example of platforms: MinGW, Cygwin, OpenBSD, NetBSD, xWorks RTOS, etc. We support POSIX-compatible platforms. Do OpenBSD and NetBSD need special care? Yes, because our support is GNU/Linux-centri

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Victor Stinner
2017-11-06 23:07 GMT+01:00 Antoine Pitrou : > The reason that testing on > them is interesting, IMHO, is to chase potential Linux-isms in our code > base. Circumventing {Free,Open,Net}BSD-specific deficiences is not. Serhiy found at least an interesting issue thanks to OpenBSD, a bug in memory de

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Antoine Pitrou
On Mon, 6 Nov 2017 22:49:06 +0100 Victor Stinner wrote: > > CPython already contais 11 "#ifdef (...) __OpenBSD__" in C and 11 > sys.platform.startswith('openbsd') in Python. Supporting a "POSIX" > platform requires some changes :-) Yes... So, the question is: does OpenBSD already maintain a Pyth

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Victor Stinner
2017-11-06 22:16 GMT+01:00 Steve Dower : > I don't believe CPython *partially* supports any platforms - either they are > fully supported or they are not supported. Ok. So there are two questions: * Where is the list of platforms "endorsed" by CPython ("fully supported") * How can we decide when

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Victor Stinner
2017-11-06 22:24 GMT+01:00 Antoine Pitrou : > We support POSIX-compatible platforms. Do OpenBSD and NetBSD need > special care? Aha, "POSIX", you are funny Antoine :-D If it was a single #ifdef in the whole code base, I wouldn't have to start such thread on python-dev :-) Open issues with "Ope

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Antoine Pitrou
On Mon, 6 Nov 2017 18:41:30 +0100 Victor Stinner wrote: > > Example of platforms: MinGW, Cygwin, OpenBSD, NetBSD, xWorks RTOS, etc. We support POSIX-compatible platforms. Do OpenBSD and NetBSD need special care? Regards Antoine. ___ Python-Dev mai

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Steve Dower
On 06Nov2017 0941, Victor Stinner wrote: [SNIP] But the question here is more about "partial" support. While changes are usually short, I dislike applying them to Python 2.7 and/or Python 3.6, until a platform is fully support. I prefer to first see a platform fully supported to see how much ch

Re: [Python-Dev] Partial support of a platform

2017-11-06 Thread Skip Montanaro
> The PEP 11 has a nice description to get a *full* support of a new platform: > https://www.python.org/dev/peps/pep-0011/ PEP 11 defines the endpoint, full support, and several requirements to call a platform fully supported. It would be nice if a process was defined for getting from "no support"