➜

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.

classification
Title: ModuleType.__new__ crash
Type: Stage:
Components: Interpreter Core Versions: Python 2.2
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: gvanrossum Nosy List: gvanrossum, nascheme, nobody
Priority: high Keywords:

Created on 2002-03-12 18:12 by nascheme, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Messages (3)
msg9656 - (view) Author: Neil Schemenauer (nascheme) * (Python committer) Date: 2002-03-12 18:12 
Submitted on behalf of Gustavo Cordova
<gcordova@hebmex.com>:

Hi all, sorry for posting to this list.

I found a (maybe?) new bug, which crashes the interpreter.
Just do this (is't repeatable):

>>> from types import *
>>> mod = ModuleType.__new__(ModuleType)
>>> mod

Upon trying to do a str(mod) to print it (I believe),
the VM crashes and burns.

I was searching for a way to construct a new module
from it's file's compiled bytecode (just read() the
"*.pyc" file),
so I thought maybe the ModuleType had some kind of
constructor
which could use the compiled byte code.

I don't have web access, so I couldn't post it as a bug
report in sourceforge.
msg9657 - (view) Author: Nobody/Anonymous (nobody) Date: 2002-03-12 20:35 
Logged In: NO 

I've got a fix. Will check in soon. --Guido
msg9658 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2002-03-12 20:37 
Logged In: YES 
user_id=6380

Fixed in CVS, moduleobject.c rev 2.41.
History
Date User Action Args
2022-04-10 16:05:05adminsetgithub: 36246
2002-03-12 18:12:28naschemecreate