question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Kombu 4.2.2 PyPi package does not match GitHub release/tag changelog

See original GitHub issue

It seems the kombu-4.2.2 package that was released (and found here https://pypi.org/project/kombu/#files) does not actually reflect the v4.2.2 tag/release on GitHub. It appears instead to be built from master.

$ unzip kombu-4.2.2-py2.py3-none-any.whl
Archive:  kombu-4.2.2-py2.py3-none-any.whl
<snip>

$ head kombu/compression.py
"""Compression utilities."""
from __future__ import absolute_import, unicode_literals

from kombu.utils.encoding import ensure_bytes

import bz2
import zlib

_aliases = {}
_encoders = {}

Compare the above with compression.py on v4.2.2.

We found this by chance when running on a Python installation without bz2 available.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:7
  • Comments:18 (6 by maintainers)

github_iconTop GitHub Comments

11reactions
thedrowcommented, Jan 1, 2019

I released 4.2.2post1. Again, I apologize for the inconvenience.

4reactions
weakcamelcommented, Jan 7, 2019

Great!

[ntravis] Leaving known breaking code out in the wild is definitely worse than making people pop a second update.

@ntravis True, if something went really, really horribly wrong, the last resort of removing the release might be a way out. I’m just not sure if this case was serious enough (it’d be easy to recover from by upgrade of the dependency, it didn’t crash OS, it didn’t delete anything - just wasn’t exactly what it said on the tin) to warrant that. But that’s my personal opinion and I can see why other’s view might differ.

[thedrow] I’ll do my best to avoid such mistakes in the future.

@thedrow Oh, well - mistakes will always happen, that’s only natural. What’s appreciated is the effort to remediate that - and kudos for that! 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

removal of kombu-4.2.2 from pypi #974
This broke openstack gate :| Was there a reason for it's removal? ... Kombu 4.2.2 PyPi package does not match GitHub release/tag changelog...
Read more >
celery~=4.2.1 resolved into missing kombu==4.2.2 #707
But while "Finding secondary dependencies", I saw it's trying to fetch kombu==4.2.2, which is not found in pypi. $ pip-compile -v -r
Read more >
Ability to mark a version of a package as deprecated or ...
kojiromike mentioned this issue on Jan 17, 2019. Kombu 4.2.2 PyPi package does not match GitHub release/tag changelog celery/kombu#966.
Read more >
Release of kombu==4.6.0 is breaking celery==4.3.0 #5570
Optional Debugging Information. I have tried reproducing the issue on more than one Python version and/or implementation.
Read more >
poetry add celery fails because kombu==4.2.2 exists as ...
... install kombu==4.2.2. I don't know if this is a pip bug or "feature". ... [PackageNotFound] Package kombu (4.2.2) not found. # ...snip....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found