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-16.11:01:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <e81aadd1-9c82-7e90-084b-c7a0ff568a20@egenix.com>
In-reply-to <1634340673.74.0.0592710372571.issue45395@roundup.psfhosted.org>
Content
On 16.10.2021 01:31, Eric Snow wrote:
> 
> @MAL, who's maintaining Tools/freeze?  I'm not aware of who's using it (other than you, of course).  It looks like PyRun isn't compatible with anything newer than 3.5, so it seems like that isn't verifying that Tools/freeze still works.  Neither does it have tests that run in the test suite (nor on buildbots).
> 
> So could Tools/freeze have been broken for a while?  I ask because I haven't been able to get it work work on the master branch (or on 3.10).

I don't know who maintains it, but it's been working fine up until Python 3.8,
which is the last version I ported PyRun to.

There have also been a couple of patches going into the freeze tool, so this is
still on the radar of at least some people other than me. It's also one of the
oldest tools we have in Python and dates back to the early days of Python. Guido
wrote the initial version.

I can try to port PyRun to 3.9 and 3.10 to see whether I run into any issues.
Would that help ?
History
Date User Action Args
2021-10-16 11:01:05lemburgsetrecipients: + lemburg, brett.cannon, eric.snow
2021-10-16 11:01:05lemburglinkissue45395 messages
2021-10-16 11:01:04lemburgcreate