This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients brett.cannon, eric.snow, lemburg
Date 2021-10-15.12:11:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <d0132723-8637-f1f3-d2ca-496f83a09c84@egenix.com>
In-reply-to <1634245017.41.0.447111612436.issue45395@roundup.psfhosted.org>
Content
On 14.10.2021 22:56, Eric Snow wrote:
> 
> @MAL, what's the best way to make sure Tools/freeze is still working?  I don't see any tests for it in the test suite.  I tried running the test in Tools/freeze/test, but I can't get that to work on main (or on the 3.10 branch).

You'd have to create a frozen binary using the standard way freeze
works. I have never run those tests, so don't know whether they work,
but, of course, made sure that the freeze works as basis for PyRun
and patched it slightly to add features we needed.

One of these days, I need to refactor PyRun into a standalone project
and put it on Github (it's currently integrated into our internal
single repo setup). Then it'll be easier to see the changes I made.
For now, I can only reference the tar file:

https://www.egenix.com/products/python/PyRun/#Download
https://www.egenix.com/products/python/PyRun/#Installation

I can send you an updated version for Python 3.8, if there's
interest.

Essentially, you need to create a Python module which runs your
application, then point freeze.py to it and then compile the
generated .c files using the generated Makefile.
History
Date User Action Args
2021-10-15 12:11:18lemburgsetrecipients: + lemburg, brett.cannon, eric.snow
2021-10-15 12:11:18lemburglinkissue45395 messages
2021-10-15 12:11:17lemburgcreate