Summary: | dev-python/celery-3.0.18 bump/test failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/celery/celery/issues/1321 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrick Lauer
2013-04-16 02:26:26 UTC
latest works was intended for 466080 requires a kombu-2.5.10.ebuild yep I got the same. Comment 2; even got the right bug wrong, 465960 -> 466080, off day that day. Seeing the maker iksaif has become rare or absent, not sure which, as I understand, this package opens a pandora's box. Issue of the URL tells us there's a 3.0.19 which passes and quote "Not much we can do about it for 3.0.18" In a migrated form we get in 3.0.19 in the dep list sql? ( dev-python/sqlalchemy[$(python_gen_usedep python2_7)] )" test? ( -------------------------------------------------------------- dev-python/sqlalchemy[$(python_gen_usedep python2_7)] dev-python/pymongo[$(python_gen_usedep python2_7)] --------------------------------------------------------------- doc? ( ---------------------------------------------------------------- dev-python/sqlalchemy[$(python_gen_usedep python2_7)] Over time py3 and pypy support are being added to various packages in portage, and we end up with this technically being whittled down to PYTHON_COMPAT=( python{2_7 ) by virtue of being tied to the lowest common denominator in the dep list, making a mockery or a waste, toss a coin, of celery actually equipped to handle py3 and pypy. the use sql can be dropped, but then the same trap occurs with dev-python/sqlalchemy[$(python_gen_usedep python2_7)] under doc? ( sqlalchemy basically mirrors this fiasco but on a larger scale. 3.0.19 in portage. 3.0.18 has been skipped |