#6 add build instructions regarding python 2.x and python 3.x
Opened 7 years ago by pavlix. Modified 7 years ago

When installed directly from git, fedora-packager-setup (and possibly other commands) uses /usr/bin/python as interpretter and therefore should work with both 2.x and 3.x (otherwise python2 or python3 should be used). This is automatically handled for packages that use distutils but not with fedora-packager-setup. The PYTHON variable selects a single python version to built the library but with /usr/bin/python in shebang the library should actually be built for both 2.x and 3.x to ensure that it can be run with either of them depending on local configuration.

$ fedora-packager-setup 
Traceback (most recent call last):
  File "/usr/bin/fedora-packager-setup", line 21, in <module>
    import fedora_cert
ImportError: No module named 'fedora_cert'

See also: https://github.com/pavlix/gentoo-fedora/issues/1

Not interested in this any more as I made things work with Python 3.x already.

python3 is not supported currently. and there is no instructions on how to build it for python3. I am interested in what you did to have it work. I am honestly not sure if all of the deps support python3

@ausil Thanks!

I can't claim anything about all the dependencies, I am modifying the tools while using them. That means that dependencies work for the actions I actually tried well enough either in their upstream versions or with patches I already posted to the respective projects. Let me know if there's anything I can do to test more thoroughly than by casual usage.

Anyway, this particular issue should be closed because the problem with fedora_cert was related to the gentoo ebuild I created. The current version works for me.


I'm not using any additional patches and as you see the ebuild doesn't do any special magic. So basically you can claim at least basic Python 3.x support in fedora-packager as you already have a user. The magic functions in the gentoo ebuild just run make and make install multiple times with different environment (including the PYTHON variable).

I'm tracking Python 3.x compatibility of some other tools here:


Login to comment on this ticket.