Martin v. Löwis wrote: > Thomas Heller wrote: >> But if you make the change to implement option 3, IMO it would be a >> good idea to add the Python version number to the .pyd basename as >> well. > > Can you please elaborate? In the name of what .pyd file do you want > the Python version number? And why?
Since on Windows binary extensions have to be compiled for the exact major version of Python, it seems logical (to me, at least), to include that version number into the filename. Say, _socket25.pyd. > And why is that related to not supporting extensions with .DLL names > anymore? IMO changing that would require a PEP (but I may be wrong), and this is only another idea which should be considered when writing or discussing that. If you don't like the idea, or don't see any advantages in this, I retract the request. >> pywin32 already has to do this, since pythoncomXY.pyd and >> pywintypesXY.pyd have to live (if possible) in the windows >> directory. > > I think this is a very special case: it could have been implemented > with separate DLLs which just provide the COM entry points, and find > the location of pythoncom.pyd from the registry. I would discourage > people from providing additional entry points to an extension module. > > > Regards, Martin _______________________________________________ > 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/python-python-dev%40m.gmane.org > > _______________________________________________ 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
