[issue10081] 'import' operator doesn't work with unicode non 7-bit ASCII module names (OS: windows)

2010-10-13 Thread Valery Lesin 

New submission from Valery Lesin valery.le...@gmail.com:

OS: windows

The attempt to import module with non 7-bit ASCII name results in 
'ImportError: No module named module name' exception.


Some thoughts: import.c uses functions like fopen, stat and FindFirstFile which 
wouldn't work correctly with non 7-bit ASCII filenames in Windows.

--
components: Interpreter Core, Unicode
messages: 118505
nosy: Valery.Lesin
priority: normal
severity: normal
status: open
title: 'import' operator doesn't work with unicode non 7-bit ASCII module names 
(OS: windows)
type: behavior
versions: Python 3.1, Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10081
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10082] PyRun_SimpleFile crashes application

2010-10-13 Thread Valery Lesin 

New submission from Valery Lesin valery.le...@gmail.com:

All the functions in Python/C API for file execution (like PyRun_SimpleFile) 
crash the application.

Some thoughts about problem: these functions use FILE* as first parameter which 
is binary incompatible with different CRT (python.dll and application could use 
different ones). 

Some thoughts about solution: maybe it's possible to pass only filename and 
python will open (and close) file itself? Second idea is to use functions like 
PyFile_FromString (like in Python 2)

--
components: Extension Modules, Windows
messages: 118506
nosy: Valery.Lesin
priority: normal
severity: normal
status: open
title: PyRun_SimpleFile crashes application
type: crash
versions: Python 3.1

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10082
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10082] PyRun_SimpleFile crashes application

2010-10-13 Thread Valery Lesin 

Valery Lesin valery.le...@gmail.com added the comment:

OS: windows xp
Compiler: MSVC versions 7.1, 8.0 and 9.0 

Actually, the difference in compiler for python library and client applications 
causes the problem (I suppose that even same compiler with different options 
could give binary incompatible FILE structures).

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10082
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10068] global objects created in some module are not destroyed when last reference to that module is released

2010-10-12 Thread Valery Lesin 

New submission from Valery Lesin valery.le...@gmail.com:

Interpreter: Python 3.1.2

Sample:

= first.py =
import sys
import second 

if 'second' in sys.modules:
  print ('in sys modules')
  del sys.modules['second']

del second

= second.py =
class A:
 def __init__(self):
   print('created')

 def __del__(self):
   print('destroyed')

a = A()
-

Result: 'destroyed' isn't printed
With Python 2.6.5 it worked fine

--
components: Interpreter Core
messages: 118408
nosy: Valery.Lesin
priority: normal
severity: normal
status: open
title: global objects created in some module are not destroyed when last 
reference to that module is released
type: behavior
versions: Python 3.1, Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10068
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com