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
Fix version parsing #339
Fix version parsing #339
Conversation
Ping @dagolden, @ribasushi, @Leont, @karenetheridge, @rjbs in case you have any input on this. |
Also ping @shadowcat-mst, @miyagawa and @neilbowers. Anything to add? |
I'm only following this issue lightly, but I don't think version.pm's handling of underscores is well-advised, and historically did particularly perverse things depending on presence/absence of version.pm and the version of perl (see "Version Number Puzzles" for examples). And that's only for modules, not for distributions, where version numbers are irrelevant to PAUSE except for the presence/absence of underscores. Generally speaking, the use of underscores in version numbers is a historical accident and cause more problems than it solves. Treating them as invisible for all purposes except deciding whether or not to index a distribution should solve more problems than it creates. The Lyon 2014 "version number summit" agreed on this as the desired direction for handling of version numbers: https://gist.github.com/dagolden/9559280. |
I agree; let's stick to the decisions made at the version number summit (which needs a better name - what was the name of that restaurant?) I'm also hoping that this will fix #284. |
The current implementation of MetaCPAN's numification leads to issues like miyagawa/cpanminus#377 (comment) on cpanm. +1 on this patch. |
This fixes the version number parsing to handle underscores properly.
version.pm is too buggy to use for this.
Fixes #337