Coder Social home page Coder Social logo

Versioning issues about py-amqp HOT 2 CLOSED

celery avatar celery commented on May 25, 2024
Versioning issues

from py-amqp.

Comments (2)

ask avatar ask commented on May 25, 2024

The version in amqp/__init__.py from

https://pypi.python.org/packages/source/a/amqp/amqp-1.0.13.tar.gz#md5=33e9e59f71a396f9cdd5d5d6a3d2e5d5

is most certainly 3.0.13

Probably you have installed the development previously, and pip will not downgrade until you have uninstalled it!

from py-amqp.

saschpe avatar saschpe commented on May 25, 2024

Whatever "3.0.13" means... It is also not important which version the current tarball contains. What matters is that there has been a release in the past with a version number higher than the current one.

Let me explain a bit more what issue we have. openSUSE is a distribution that provides stable releases. These include Python modules packaged as RPMs. One of the most important commitments Linux distributions offer their users is upgradability. So let's say a user of openSUSE-12.3 (the current release) has python-amqp-1.2.0.rpm (slightly simplified) installed. If we would release python-amp-1.0.13, his package manager wouldn't care since the version is inferior. Of course we do have solutions for this, we can either fake a different version (sometimes done in the Debian / Ubuntu world) like 1.2.0+really1.0.13 or use an RPM epoch (check the interwebs). Both are rather ugly. BTW. here's a summary of how both DEB and RPM compare versions: https://twiki.cern.ch/twiki/bin/view/Main/RPMAndDebVersioning

Therefore, we (and all the other major distros) simply don't allow version downgrades. So this is an issue outside of virtualenvs or local pip caches. py-amqp seems to losely follow semantic versioning. Even in this scheme, a version downgrade is a no-go. Unfortunately, it's a bit challenging to dig out py-amqp's past releases since they are hidden from PyPI (which is the default setting). So in the past, 1.2.0 was out there and unfortunately we packaged it at this moment.

Long story short, I don't think the issue is solved already and I would love to see a proper resolution. Even if you wouldn't want to bump to 1.2.1 to provide a proper upgrade path, it would at least help if we could be sure that this won't happen again.

from py-amqp.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.