-
Notifications
You must be signed in to change notification settings - Fork 15
Fix @ parsing in versions #162
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
base: master
Are you sure you want to change the base?
Conversation
Why the heck would @ be part of a package name? |
Come to think of it shouldn't. I thought maybe it was from some requires format, but that's not a thing. Hmmm, I'm digging into where the @ is coming from. Probably an errant usage of the pretty print format for a specific version. |
That makes more sense. An old package of mine had an Now the |
|
True, it is. Perhaps it should check for any non-ascii char that's not in the version char set? Not sure it's official, but Nimble packages seem to be ascii limited, or perhaps should?
I thought about that, but it'd be a pain. It'd have to go through the Nimble parser and just end up with the same result of skipping that Nimble release. |
Use strutils.PunctuationChars except the chars we need, >= etc, depending on the logic. |
* update updates * update updates * update * update * update * update * update * swap to option to represent no answer * swap to option to represent no answer from isOutdated * swap to option to represent no answer from isOutdated * rename * rename * rename again
Unfortunately that doesn't work since we can have URLs in the name component. Still I tried to generalize it a bit more using Version strings are checked for incomplete parsing ignoring dangling whitespace. Also I discovered I'm not the only one who's gone from |
Dependency versions would get messed up with
@
being added to the pkg name in some cases.