![](https://secure.gravatar.com/avatar/a0f69035374239eb554cf5d7f4ef1f4f.jpg?s=120&d=mm&r=g)
I want to get the last XXX removed from PEP 241 so it can be posted to c.l.py.a and python-dev *today*. The missing bit is: Platform (multiple use) A (XXX whitespace? comma?)-separated list of platform specifications. Platform specifications are limited to the following list: XXX copy list from PPD? SourceForge? Example: 'XXX' So, what to do? Some options are: * Specify a short and incomplete list of platform specs: MacOS/Windows/POSIX/BeOS/... State in the PEP that this list is incomplete. Binary distributions will use a different metadata header (Compiled-Platform, Supported-Platform, or something like that) to specify the OS and CPU they were compiled for. * Leave 'Platform' to be filled in for binary distributions. Developers should put platform limitation notes in the 'Description'. I lean toward #1, and if I don't hear any strong reasons to do otherwise, that's what I'll check it and post, sometime after 5PM EST. --amk
![](https://secure.gravatar.com/avatar/dd2f9ae30e177757d76e1b2749558132.jpg?s=120&d=mm&r=g)
On Mon, 19 Mar 2001, Andrew Kuchling wrote: [...]
So, what to do? Some options are:
* Specify a short and incomplete list of platform specs: MacOS/Windows/POSIX/BeOS/... State in the PEP that this list is incomplete. Binary distributions will use a different metadata header (Compiled-Platform, Supported-Platform, or something like that) to specify the OS and CPU they were compiled for. [...]
Sounds okay. Is there any reason not to use the os.name values for this? ie. 'nt', 'dos', 'posix', 'mac', 'os2', 'java', 'ce' etc ('beos' doesn't seem to be in the list for 2.0 -- was it a recent port, or what?) John
participants (2)
-
Andrew Kuchling
-
John J. Lee