| Summary: | dev-python/python-dateutil-2.0 version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Stanislav Ochotnicky (RETIRED) <sochotnicky> |
| Component: | [OLD] Library | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Stanislav Ochotnicky (RETIRED)
2011-05-08 18:48:37 UTC
Arfrever, will it work to just have a dateutil-2.0 setting the right PYTHON_ABIS stuff for 3.x and 1.x setting the PYTHON_ABIS for 2.x? For example, will that make portage install both versions if I have different Pythons installed? I'm guessing it's not that simple... What if we slot them? shouldn't that allow to get 1.x and 2.x installed at the same time depending on the versions of installed Python? dev-python/python-dateutil-2.0 has been added to Progress Overlay. dev-python/python-dateutil-1.5 uses SLOT="python-2". dev-python/python-dateutil-2.0 uses SLOT="python-3". Packages, which support Python 2 and Python 3 and need dev-python/python-dateutil, will use: RDEPEND="... $(python_abi_depend -i "2.*" dev-python/python-dateutil:python-2) $(python_abi_depend -i "3.*" dev-python/python-dateutil:python-3) ..." in cvs. |