-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing of version failed #9
Comments
Thanks for the feedback. I must admit, I have replaced |
I haven't given much thoughts but I think you could try to let-bind TBH, I don't know why/where it is used in pippel but I think parsing versions is a hard problem. 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. |
Thanks for the advice. I do appreciate that. For now I will exclude version strings with letters from comparison by 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. |
Closed since this issue seems to be handled in (764c8e) |
Hello,
It looks like you are using
version-to-list
to parse the packages' version but the version formats supported by Emacs are different from those of PEP 440.For example, I have a package which seems to have a pre-release version (https://www.python.org/dev/peps/pep-0440/#pre-releases) incompatible with version to list.
I can see the following error in my
*Messages*
buffer:And the
pippel-list-packages
seems to have broken, it won't complete but the minibuffer is now inaccessible due to the "Pip processing..." message still being updated indefinitely.I don't know if you should temper with
version-regexp-alist
or not.And some positive feedback,
Great idea of packages! 👍
The text was updated successfully, but these errors were encountered: