Éric Araujo <mer...@netwok.org> added the comment:

I don’t think warnings should be removed, at least not by default.  They’re 
warnings, not errors, which is IMO a nice compromise between accepting anything 
and requiring that rules be followed.  We could add an option like 
--no-warnings in distutils2, but I’m worried people could just disable it 
globally instead of fixing the actual problems.  I’m inclined to reject this 
report.  Tarek, opinion?

Since the warnings go to stderr, you can suppress them with shell redirection, 
although I wouldn’t advise that since you could miss unrelated warnings or 
errors.  Does that cover your need?

*musing* Maybe we could revamp the required fields.  Name and version are 
required by various distutils[2] and pkgutil APIs, so not setting them will 
screw up queries or uninstallation for example.  We could make distutils2 fail 
when they’re not present.  But then, why not fail if a distribution to be 
installed has the same name+version that an already present distribution?  What 
I’m saying is that it’s better to do no checks than incomplete checks, and this 
is the realm of a distribution manager, not the underlying library, but then 
again, distutils2 provides a simple distribution manager too, so I’m not sure 
this should be in or out of it, and at which level (lib/command/manager).

(Removing Terry from nosy at his request in private email.)

----------
nosy: +eric.araujo -terry.reedy

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue7726>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to