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, corona10, eric.snow, lemburg
Date 2021-10-21.22:41:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <8a1961dd-d6e3-d871-6e48-3f925d524653@egenix.com>
In-reply-to <1b8c02e2-987c-66e1-9bce-a637a557b8b3@egenix.com>
Content
I have an initial version of PyRun for Python 3.10 running as well.
This created a few more headaches in order to make it work with
setuptools and some glitches which appear to be bugs in 3.10
(https://bugs.python.org/issue45563 and https://bugs.python.org/issue45562).
Nothing major, though.

I'll have to check my version of the freeze tool against the one
in Python 3.9 and 3.10 to see whether there's anything in the
core versions which could cause the tool not to work.

BTW: (My) freeze.py uses this startup code as main():

int
main(int argc, char **argv)
{
        extern int Py_FrozenMain(int, char **);

        /* Disabled, since we want to default to non-optimized mode: */
        /* Py_OptimizeFlag++; */
        Py_NoSiteFlag++;        /* Don't import site.py */

        PyImport_FrozenModules = _PyImport_FrozenModules;
        return Py_FrozenMain(argc, argv);
}

I still have to dig through the changes you have made, but this
suggests that it replaces PyImport_FrozenModules completely
with its own version, so the default freeze that you are
implementing gets overridden.
History
Date User Action Args
2021-10-21 22:41:55lemburgsetrecipients: + lemburg, brett.cannon, eric.snow, corona10
2021-10-21 22:41:55lemburglinkissue45395 messages
2021-10-21 22:41:55lemburgcreate