Message157656
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. |
|
Date |
User |
Action |
Args |
2012-04-06 10:33:49 | rik.poggi | set | recipients:
+ rik.poggi, tarek, eric.araujo, SilentGhost, swamiyeswanth, gotcha, berker.peksag |
2012-04-06 10:33:49 | rik.poggi | set | messageid: <1333708429.39.0.047053999447.issue11060@psf.upfronthosting.co.za> |
2012-04-06 10:33:48 | rik.poggi | link | issue11060 messages |
2012-04-06 10:33:48 | rik.poggi | create | |
|