Include freeze.py

[devicenull]

CPython has the freeze.py tool: https://github.com/python/cpython/tree/2.7/Tools/freeze

However, this doesn't seem to get included with the python27-tools package, though it is included with python33, python34u, python35u, and python36u.

However, by itself this isn't going to work. It needs the static library libpython2. 7.a to be build as well. Looking through the spec file, I see there's a patch that explicitly disables this:
https://github.com/iuscommunity-pkg/python27/blob/master/SPECS/python27.spec#L392

I can't seem to figure out what bug that references (550692 doesn't appear to be at all related in the public RHEL bug tracker, and my searches are only turning up references to spec files.

[carlwgeorge]

Thanks for bringing this to our attention @devicenull. We fork our spec files from Fedora, and that is where the patch originated from. A similar patch exists for python3 as well. Checking Fedora, their python2 package still doesn't have freeze.py, but their python3 package does. I can't find the what bug 550692 is either.

Does that tool work in our python36u-tools package? Or for that matter, can you get it to work in Fedora's python3-tools?

[devicenull]

It doesn't actually work with 36u:

# python3.6 /usr/lib64/python3.6/Tools/freeze/freeze.py
Error: needed directory /usr/lib/python3.6/config-3.6m not found
Use ``/usr/lib64/python3.6/Tools/freeze/freeze.py -h'' for help

If I fix that with a symlink, and install python36u-devel

ln -s /usr/lib64/python3.6/config-3.6m-x86_64-linux-gnu /usr/lib/python3.6/config-3.6m
yum install -y python36u-devel

I end up getting an error about:

gcc: /usr/lib/python3.6/config-3.6m/libpython3.6m.so: No such file or directory

And if I fix that with another symlink:

ln -s /usr/lib64/libpython3.6m.so /usr/lib/python3.6/config-3.6m/libpython3.6m.so

freeze ends up working ok.

The correct bug here appears to be https://bugzilla.redhat.com/show_bug.cgi?id=556092

[carlwgeorge]

If you can get it working just by adding some symlinks, it probably doesn't have anything to do with the static library files.

We are using the altinstall feature of the upstream Makefile, and it sounds like the freeze tool might need some fixes to find the correct paths. I'll keep investigating to see if we can get a patch figured out for our packages (and maybe to send upstream as well).

[carlwgeorge]

I can reproduce the same error on Fedora's python3, so it doesn't have anything to do with using install versus altinstall.

Also, I noticed this message in the doc string:

The script should not use modules provided only as shared libraries;
if it does, the resulting binary is not self-contained.

I'm guessing that is related to the static library files. So it would seem that with the patch to disable the static libraries, the freeze tool won't work as intended (like you originally pointed out). Between that, the /usr/lib -> /usr/lib64 stuff, and other customizations that we inherited from Fedora, I don't think this is something that we will tackle ourselves. Please report it to Fedora and see if they are interested in fixing it themselves. My opinion is that they should either fix the freeze tool or remove it from their packages. If they do fix it, we can import their solution to our packages.