Hi Éric, On Jun 07, 2011, at 05:30 PM, Éric Araujo wrote:
Just two things I thought about while perusing my archives yesterday.
#. For modules which are also packages, the module namespace > SHOULD include the ``__version__`` attribute.
I’m still not sure “module namespace” will be clear to everyone.
Really? We know what a module is, and we know what a namespace is, so given the context, I think it should be clear.
FYI, I noticed that PEP 382 (namespace packages) says “the namespace package itself” to refer to the corp/__init__.py file of the corp.somelib package. In the Python tutorial, we have things like “the __init__.py code”. So it looks like there’s no agreed term to refer to this module.
So, what *should* we call this thing? Note that in the PEP, I'm specifically talking about the namespace, not the file. Maybe "module's namespace" would be clearer?
A note about the setup.cfg field used to get the version from a file: It will definitely need to use another name than “version”: Tarek wants the setup.cfg field to be a direct translation from PEP 345 (modulo case insensitivity), so the description-file is another field, and version-file should certainly be one too. (I hope it’s short enough to comply with your wish of keeping the common case simple.)
The PEP currently uses `version-from-file` which seems okay to me. Would that work? -Barry