Re: 'pydo' as package name for PyDO2
Jacob Smullyan <[email protected]> Mon, 30 May 2005 13:40:28 -0400
| Newsgroups | gmane.comp.web.skunkweb |
|---|---|
| Message-ID | <[email protected]> |
On Mon, May 30, 2005 at 06:26:53PM +0100, Hamish Lawson wrote: > Jacob Smullyan wrote: > > >Now, "pydo" would be my first choice, except that PyDO1 may currently > >be in use on case-insensitive platforms, and then there would be a > >conflict, presumably. Is this important to anybody? If there were a > >conflict, it could be resolved by renaming PyDO1 to "PyDO1". > > I think we can resolve the name conflict while avoiding the potential > code breakage of renaming "PyDO" to "PyDO1". Instead we can take > advantage of Python 2.3's ability to import from zip files and the fact > that the contents of a zip file are case-sensitive regardless of the > platform. Supplying PyDO 1 and PyDO 2 as zip files allows those on > case-insensitive platforms such as Windows to have both installed > without conflict, as demonstrated by my test below: > > >>> import pydo > Hello from pydo > >>> import PyDO > Hello from PyDO > >>> Very clever. "pydo" it is, then. j -- Jacob Smullyan
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCm1AMuqamFyFXXLIRAvmYAJ47MKXuIyOICNQR8MgJvrPLtngUxQCgyFiy vKN8+j3dxT5dPSAU4ssAnfI= =nlYt -----END PGP SIGNATURE-----