'latest version' on pypi is incorrect about django-markwhat

[Alir3z4]

I think by removing the old versions the problem will be solved ?
On Apr 12, 2015 7:43 PM, "nikolas" [email protected] wrote:

I'm not sure how we would resolve this, but on the pypi page:
https://pypi.python.org/pypi/django-markwhat/1.3

The 'latest version' points to version 2014.9.20, when it should be
version 1.3.

—
Reply to this email directly or view it on GitHub
https://github.com/Alir3z4/django-markwhat/issues/21.

[nikolas]

Possibly, but keep in mind that anyone's packages that rely on version 2014.9.20 with pip will then break until they update to 1.3. It may be the only option, though.

[Alir3z4]

We can still get back to the date based version numbering..

Just saying...
On Apr 13, 2015 6:30 PM, "nikolas" [email protected] wrote:

Possibly, but keep in mind that anyone's packages that rely on version
2014.9.20 with pip will then break until they update to 1.3. It may be
the only option, though.

—
Reply to this email directly or view it on GitHub
https://github.com/Alir3z4/django-markwhat/issues/21#issuecomment-92380406
.

[nikolas]

Yeah, true. I think the bottom line is that we should pick one version scheme or the other, even if that means removing a version from the archive. Having the two schemes is confusing, and messes up pypi and automated tools like piprot.

I would prefer the incrementing version scheme like 1.3, 1.4, because it's more typical of projects on pypi, and we actually should remove version 2014.9.20 from pypi. What do you think?

[Alir3z4]

Holly miow miow, such a shame, I didn't know about piprot.

Your comment, make sense, I'll remove the older versions from pypi keep using incrementing version scheme.

Thanks ;)

[Alir3z4]

@nikolas I've removed the date scheme based versions from the pypi.
Soon I'll release a new version with commonMark changes ;).