Invalid version referenced in pypyodbc package pypyodbc-1.3.5.2.zip

[sliverc]

The pypi package pypyodbc-1.3.5.2.zip still has version 1.3.4 referenced in it's setup.py which leads to following warning message when upgrading with pip:

Requested pypyodbc==1.3.5.2 from https://pypi.python.org/packages/ea/48/bb5412846df5b8f97d42ac24ac36a6b77a802c2778e217adc0d3ec1ee7bf/pypyodbc-1.3.5.2.zip#md5=9f262beb1aebf7556fce26cad2c5d462 (from -r requirements.txt (line 15)), but installing version 1.3.4

I guess it is best to keep the version in setup.py in sync with the pypi package version.

[salteggs]

I am seeing the same problem... The current available versions on pypi are 1.2.1, 1.3.0, 1.3.1, 1.3.2, 1.3.3.1, 1.3.4.3, 1.3.5.2. However pypi installs the following:

• 1.3.2 => 1.3.2
• 1.3.3.1 => 1.3.3
• 1.3.4.3 => 1.3.4
• 1.3.5.2 => 1.3.4

This results in the package being reinstalled for versions > 1.3.2.

I'm going to stick to 1.3.2 for now since 1.3.3 is for time out support, 1.3.4 seems to be a re-release and 1.3.5 is not mentioned in the history page.

[fouvry]

This also leads to the odd situation that pip list --outdated gives the package as outdated, but when one tries to update it, it installs the 1.3.4 version (which is particularly odd if that version is already installed).

[gordthompson]

This issue appears to have been fixed by commit 042c6fd so it should no longer be a problem after the next release.

[rolweber]

AIUI, the next release will use the version number defined here:
https://github.com/jiangwen365/pypyodbc/blob/master/pypyodbc.py#L29

Still looks as if version 1.3.6.x will report as version 1.3.6, without patchlevel.
But maybe the next version will be published as 1.3.6, without patchlevel, as well.

[MRigal]

@jiangwen365 it might be time to release a 1.3.6 version.
The actual version mismatch is pretty annoying for all reinstalls, updates and outdated info...

Thanks in advance!

[matiasmlforever]

Any comments on how to actually install 1.3.5.2?

[gordthompson]

@matiasmlforever - My impression was that pip install pypyodbc actually did install from pypyodbc-1.3.5.2.zip on PyPI, but once installed it reported its version as 1.3.4. If that is not the case (and it really is installing the older 1.3.4 code) then you might try

pip install git+https://github.com/jiangwen365/pypyodbc@044227a7c67e5322f4ec4368c92680d9a696bc44

[rolweber]

The current versioning scheme with four components doesn't comply with PEP 440:
https://www.python.org/dev/peps/pep-0440/#examples-of-compliant-version-schemes

The smoothest path forward would be to release a version 1.4.0, and then stick to three components. I don't have time to come up with a PR though :-(

[nickolay]

...then you might try

pip install git+https://github.com/jiangwen365/pypyodbc@044227a7c67e5322f4ec4368c92680d9a696bc44

Note that this might report it "Successfully installed pypyodbc-1.0.5" due to an incorrect version in setup.py of that revision.

Also this didn't help me convince pipenv the pypyodbc is properly installed. I ended up using the fork that's being set up in #107:

$ pipenv install git+https://github.com/pypyodbc/[email protected]#egg=pypyodbc