Tracker bug for gentoolkit-0.2.5
Created attachment 179571 [details] setup.py python distutils installer for djanderson's rewrite of equery
Created attachment 179735 [details] setup.py (All of the changes described below are intended to be transparent to the lay end-user, although in some cases they may break scripts.) Depends upon a reorganization of gentoolkit, which I describe in detail in an email to tools-portage@gentoo.org. In essence, though, it consists of the following: - python modules would be part of the gentoolkit package (so gentoolkit.equery, for example) - separate dev bits from non-dev parts - move non-python scripts to scripts folder - mangle the python stuff so it can be called from site-packages
Created attachment 179736 [details] MANIFEST.in Manifest template file for distutils -- see comment #2
I'm going to do the refactoring of equery in gentoolkit-0.3 and will skip going to 0.2.5.
Will _rc9 work with python 3? Currently my equery (which uses python2.5) from app-portage/gentoolkit-0.3.0_rc8) doesn't work with my sys-apps/portage-2.1.7.16 ... Traceback (most recent call last): File "/usr/bin/equery", line 32, in <module> from gentoolkit import equery, errors File "/usr/lib64/python2.5/site-packages/gentoolkit/equery/__init__.py", line 31, in <module> import portage File "/usr/lib64/portage/pym/portage/__init__.py", line 58 except ImportError as e: ^ SyntaxError: invalid syntax
(In reply to comment #5) > Will _rc9 work with python 3? Currently my equery (which uses python2.5) from > app-portage/gentoolkit-0.3.0_rc8) doesn't work with my > sys-apps/portage-2.1.7.16 ... That's an interesting problem. The short answer is, no, python 3 support isn't planned for 0.3.0. The traceback you got is actually due to the fact that portage 2.1.7* doesn't support python 2.5 anymore. (You can see that in its DEPEND line in the ebuild). 0.3.0 branch is tested up to py2.7 without deprecation warnings, the easiest option is to switch your default python version to 2.6 or 2.7 and reinstall gentoolkit rc8. Another option for you is to run 2to3 over the source and use python 3. I haven't tried it, but I imagine it applies cleanly. If you try this and come up with errors, please submit bugs. I'll try to add automatic python version detection in the next major version of gentoolkit, which shouldn't take nearly as long to get out the door as this one.
Starting March 16, I'll be unavailable to do any work or even answer questions on "my parts" of gentoolkit for an extended period of time (up to 3~4 months). I'd like to propose a feature freeze starting now so that we have at least a week to really thrash the current code base around. Any new feature bugs marked for inclusion should be postponed to the next minor version. Everyone involved okay with that?
That is fine with me. We will work forward with fixing the bugs and hopefully by the time you get available again, we will be ready for gentoolkit-0.3.1.
All depending bugs are now closed.
