[issue7517] freeze.py not ported to python3

Éric Araujo added the comment: Closing as duplicate, please use the other bug report to discuss. -- nosy: +eric.araujo resolution: -> duplicate stage: needs patch -> committed/rejected status: open -> closed superseder: -> freeze.py broken due to ABI flags ___

[issue7517] freeze.py not ported to python3

Changes by Éric Araujo : Removed file: http://bugs.python.org/file15570/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue7517] freeze.py not ported to python3

Andreas Stührk added the comment: Note that I also opened issue #11824 for the abiflags problem. -- nosy: +Trundle ___ Python tracker ___

[issue7517] freeze.py not ported to python3

Marc Sibson added the comment: I think the original issue has been fixed by http://hg.python.org/cpython/rev/fd20eba1f201. freeze.py is now broken due to pep3149 and ABIFLAGS, freeze-pep3149-compat.patch adds awareness of ABIFLAGS to Tools/freeze/freeze.py. For me "python3.3 freeze.py hell

[issue7517] freeze.py not ported to python3

Patrick Stinson added the comment: Interesting. I found it incredibly useful. I would love to fix the port (if I find the time, of course :(). On Tue, Dec 15, 2009 at 12:52 PM, Brett Cannon wrote: > > Brett Cannon added the comment: > > Almost prioritized to low as there has been talk in the

[issue7517] freeze.py not ported to python3

Brett Cannon added the comment: Almost prioritized to low as there has been talk in the past of not even supporting frozen modules by default. The tool should either get fixed or removed depending on how people feel. -- nosy: +brett.cannon priority: -> normal stage: -> needs patch t

[issue7517] freeze.py not ported to python3

New submission from Patrick Stinson : Tools/Freeze/freeze.py is still producing C code that expects the old- style module initialization functions, causing link errors. The simple example in Tools/Freeze/hello.py easily demonstrates this behavior. -- components: Library (Lib) messages: