| Summary: | Bump dev-python/pandas to 0.8.0 (released June 29th, 2012) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matt Summers (RETIRED) <quantumsummers> |
| Component: | Current packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | gorkypl |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://pandas.pydata.org/pandas-docs/stable/whatsnew.html#v0-8-0-june-29-2012 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | ebuild for pandas v0.8.0 | ||
|
Description
Matt Summers (RETIRED)
2012-07-05 19:28:11 UTC
Simply renaming the ebuild works for me, so bumping should be easy. There is also an issue with required dateutil version: https://github.com/pydata/pandas/issues/1594 (long story short: pandas requires dateutil-1.5 when used with python-2.x and dateutil 2.x when used with python-3.x, and I have no idea how this should be addressed in the ebuild). Nothing should use <dev-python/python-dateutil-2.1. dev-python/pandas should be modified to work with >=dev-python/python-dateutil-2.1, which supports both Python 2 and 3. Is it a statement that should be passed to pandas developers? (In reply to comment #4) > Is it a statement that should be passed to pandas developers? Yes. Since pandas wants python-dateutil-2.* with Python 3, it should be very easy to also use python-dateutil-2.* with Python 2. Created attachment 318268 [details]
ebuild for pandas v0.8.0
ebuild for pandas v0.8.0, is just a copy of the previous version of the ebuild. "cp pandas-0.7.3.ebuild pandas-0.8.0.ebuild".
So far all my scripts that use pandas are working properly.
Is anybody interested in bumping the package? Meanwhile pandas-0.8.1 is out, it works after renaming ebuild and fixes the bug described in comment #2, so to me it looks like a no-brainer. http://pandas.pydata.org/pandas-docs/stable/whatsnew.html I see that pandas 0.8.1 has been added to the tree, so this bug probably can be closed. |