-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tarek Ziadé wrote:
On Tue, Apr 7, 2009 at 8:47 PM, Lennart Regebro <regebro@gmail.com> wrote:
On Tue, Apr 7, 2009 at 20:18, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
If anyone wants to work on it, or comment, Some comments:
"MANIFEST.in is fine" Except that it introduces Yet Another Domain Specific Language. Wtf does "prune" mean? It's not obvious. The docs indicate that it actually excludes, but why it's not called "exclude" is then strange. We already have a language, Python. We don't need more. ;-)
And the fact that is uses a separate file doesn't help.
Yes, I know I'm just whining. But I don't agree that MANIFEST.in is fine. I think it is unfine. :)
I agree with this. Remember: I wanted to deprecate MANIFEST.in in favor of a pure python description. Then people strongly objected.
I want *less* stuff (ideally nothing) spelled in imperative Python, with some common declarative file replacing both the information currently in setup.py and MANIFEST.in. I thought we were in agreement that non-introspectable metadata was a Bad Thing(TM)? http://wiki.python.org/moin/Distutils/StaticMetadata Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3JdV+gerLs4ltQ4RAhGbAJ4in8+UOgM5GJ/3ISGfU2VHLVh4tgCg13O1 qx4oVMxLRJXHUz794mW2UyM= =pgtS -----END PGP SIGNATURE-----