Parsing of version failed about pippel

[brotzeit]

Thanks for the feedback. I must admit, I have replaced string= with version< without looking into the version formats. It seemed to work so I didn't give it any further thoughts #5. Are there any alternatives to version< or do I have to write a function, that compares the python version strings ?

[Sarcasm]

I haven't given much thoughts but I think you could try to let-bind version-regexp-alist with the pip format of pep 440.

TBH, I don't know why/where it is used in pippel but I think parsing versions is a hard problem.
So, if you don't absolutely need it, don't do it, if you need it, try to give a best effort implementation, and when people complains you can add a new test case.
One nice thing about a version comparison function, is that it is easy to unit test. 👍

If you make a script that fetch a bunch of version from the python package archive and make sure the parsing works for all of them, then it's a good first step, the occasional bug can be fixed when it happens.

[brotzeit]

Thanks for the advice. I do appreciate that. For now I will exclude version strings with letters from comparison by version<, so it should at least work for installed versions, that are older than the latest version.

But I will try if I can write a working python version string parser. This is a good opportunity to write my first unit test.

[arifer612]

Closed since this issue seems to be handled in (764c8e)