On 23 Jul, 2010, at 11:02, Barry Warsaw wrote: > On Jul 22, 2010, at 03:58 PM, Ronald Oussoren wrote: > >> I guess this is not an explicit goal of this PEP, but the structure is >> very close to supporting multiple system architectures at the same >> time. I regularly develop code that needs to run on Windows, Linux >> and OSX and it is very convenient to do so in a shared directory tree >> (locally on one machine and accessed using remote mounts on the other >> ones). This works fine for pure python code, but I currently have to >> resort to tricks for extension modules. > > [...] > >> A way to generically solve my problem is to add the platform name as >> well, such as "foo.cpython-32m-darwin.so" or >> "foo.cpython-32mu-linux2.so". > > This could certainly be done in the Windows build, but that wouldn't help > bridge the gap among different POSIX systems.
The windows port isn't a problem for this, it uses a different suffix (".pyd")
than the unix ports.
> I'd be open to adding the
> platform name to the tag, but I'd probably define it as part of the
> implementation field, e.g. foo.cpython-linux2-32m.so. Or maybe start with the
> platform name, e.g. foo.linux2-cpython-32m. This isn't a strong preference
> though.
I don't have a strong opionion, but placing the platform name at the start
is probably better to be consistent with sysconfig.get_platform().
Ronald
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
