Rik Poggi <poggi.ri...@gmail.com> added the comment: Thanks, I'll wait! In the meanwhile I couldn't help to dig a little deeper and found that the Metadata class is currently logging a warning. Should the commands raise something when there's a warning in strict mode?
I was playing with the check command about this when I stumbled in an odd looking piece of code in metadata.py with a FIXME note: "# FIXME this rejects UNKNOWN, is that right?" (see attached file). I'm not sure how, but it seems related to a "random" (I couldn't find any pattern) log message that sometimes give: "'UNKNOWN': '0.4.5dev' is not a valid version (field 'Version')" and others: "'Name': '0.4.5dev' is not a valid version (field 'Version')" (I had this with consecutive execution from a simple test that I wrote in test_command_check, with metadata['name'] == 'Name'). I hoped to not have wasted your time, but I thought that it could may be related to this bug since it seems that the version gets rightfully (but strangefully) warned as not valid from this "middle-layer" check point. ---------- Added file: http://bugs.python.org/file25141/metadata_set_extract.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11060> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
