| Summary: | Meaningless error message when python v3 is the only python available | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Scott Garman <scott.a.garman> |
| Component: | meta-yocto | Assignee: | Scott Garman <scott.a.garman> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | josh, poky.bs.watcher, poky.watcher, sgw |
| Version: | 1.0 | ||
| Target Milestone: | 1.1 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 2011-06-14: Patch submitted to poky ML | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Scott Garman
2011-05-31 14:32:25 UTC
The exception raised by quilt being missing is invalid syntax in Python. try: stuff except MyError as e: print(e) is the correct syntax for exception handling, so the error is correct though still not useful. As an aside re the support of Arch, iirc the use Python 3 by default. Ok, so this bug doesn't have to do with quilt after all - we build quilt as quilt-native, and I don't have a host version installed on any of my build machines. I've tested that pointing bitbake to a python v3 interpreter will result in the same error Mark ran into, and that is what we need to add a check for. We've checked for old versions of python, but not v3-only ones. Progress update: This is not as simple as adding a python version check in sanity.bbclass, because the v3 python interpreter cannot even parse all of the bitbake code. I'm diving through various layers of making bitbake work on python v2 and at least superficially parse on v3 so it can get to the point of running the sanity test. A hackier alternative here might be to do a python v3 test in the bitbake wrapper script? Thanks for the suggestion, Joshua. It looks like that is the only feasible way to fix this. The impasse I've reached is that module importing from within your own package has changed, and the new syntax of specifying things is not backward-compatible. So it does not appear that I can pull this off in such a way that both v2 and v3 versions of python will work - even just to get the code to pass the parsing stage. |