| Summary: | python-pandas support removed from latest yocto | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Scott Branden <scott.branden> |
| Component: | meta-yocto | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | poky.bs.watcher, poky.watcher, randy.macleod, TicoTimo |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Scott Branden
2019-08-14 16:41:35 UTC
Is this automatically supported with python3 and we don't need to RDEPENDS on python-pandas any more, just REDEPENDS on python now? The python2 version is dropped from oe-core but there is a python3 version in meta-python (meta-openembedded). Python2 is at EOL later this year. Can you use that version? Our recipe currently has RDEPENDS_${PN} = "python-pandas"
With the latest change in yocto and meta-openembedded this will not work.
So, how is pandas supported in the meta layers with python3 now?
It looks like you'd have to depend on python3-pandas: http://cgit.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python3-pandas_0.23.4.bb?h=master You could ask on the oe-dev email list if the plan is to always use the python3 prefix. It looks like that is the case at the moment to me. Oh and for anyone interested the removal was: http://cgit.openembedded.org/meta-openembedded/commit/meta-python/recipes-devtools/python?id=5f0f3e0eabddd8b1d38d276373804045ad776ceb commit 5f0f3e0eabddd8b1d38d276373804045ad776ceb Author: Alexander Kanavin <alex.kanavin@gmail.com> Date: Fri Aug 9 16:06:26 2019 +0200 python-pandas: remove the python 2.x version of the recipe As it depends on pathon 2.x Numpy which has been removed from oe-core. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Randy, thanks - will try. Such renamings cause unnecessary incompatabilties. Scott, I agree that it would be nice if the package name didn't need to change but there are some good reasons for this approach: 1. Work is required to make sure that the python3 version works well for your app so forcing you to change your dependency make sense. 2. Since python2 is becoming obsolete, using the python3 prefix makes it easier to identify python2 packages and remove them. There are probably other factors so I've CCed Tim Orling, one of the meta-python maintainers, in case he wants to comment. Randy/Tim, I should be able to specify python-pandas and it picks up whatever the currently supported version of python is. If I specifically want python3 then I should specify python3 directly via recipe names or perhaps through an environment variable specifying PYTHON_VERSION. Just the same way there are such variables as GCCVERSION? |