rdar://91296762
Details
Details
Diff Detail
Diff Detail
- Repository
- rLNT LNT
Event Timeline
Comment Actions
Is the change about handling cases where the project name is something that would not be valid for parse_version? Could you detail the commit message a little bit to explain what is currently not compliant?
Comment Actions
This showed up in one of our buildbots:
++ lnt check-no-errors lnt-submission.json lib/python3.8/site-packages/pkg_resources/__init__.py:122: PkgResourcesDeprecationWarning: LNT 0.4.2.dev0 is an invalid version and will not be supported in a future release warnings.warn( ++ echo @@@@@@@ @@@@@@@
Comment Actions
Ah right so I suggest a description along the liens of:
Call parse_version on the LNT version only to be PEP 440 compliant. Better wording welcome. LGTM with a better description
Comment Actions
This comment has been deleted.
lnt/lnttool/main.py | ||
---|---|---|
474 | I've fixed some C++ism when applying the patch or many tests were failing. |
lnt/lnttool/main.py | ||
---|---|---|
474 | Good catch, thanks! |
I've fixed some C++ism when applying the patch or many tests were failing.