Bug 791 – Pylab interferes with __moduleShutdown and prevents PySide import

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 791 - Pylab interferes with __moduleShutdown and prevents PySide import

Summary:

Pylab interferes with __moduleShutdown and prevents PySide import

Status:	CLOSED INVALID

Product:	PySide
Classification:	Unclassified
Component:	QtCore
Version:	HEAD
Platform:	PC MS Windows XP/Vista/7

Importance:	P5 critical
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-03-26 07:44 EET by jazz_vibes
Modified:	2011-04-29 18:07 EEST (History)
CC List:	10 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description jazz_vibes 2011-03-26 07:44:21 EET

This bug prevents development of scientific software. 

It can be reproduced by running at the command prompt:
ipython -pylab
>>>import PySide


Python 2.6.5 (r265:79096, Mar 19 2010, 21:48:26) [MSC v.1500 32 bit (Intel)]
Type "copyright", "credits" or "license" for more information.

IPython 0.10.1 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object'. ?object also works, ?? prints more.

  Welcome to pylab, a matplotlib-based Python environment.
  For more information, type 'help(pylab)'.

In [1]: import PySide
------------------------------------------------------------
Traceback (most recent call last):
  File "<ipython console>", line 1, in <module>
  File "C:\Python26\lib\site-packages\PySide\__init__.py", line 2, in <module>
    import private
  File "C:\Python26\lib\site-packages\PySide\private.py", line 2, in <module>
    from QtCore import __moduleShutdown
ImportError: DLL load failed: The specified procedure could not be found.

Comment 1 Gerald 2011-03-28 12:17:58 EEST

I can do this without error.  

That DLL error looks awfully similar to one I came across that seemed to be
caused by PySide loading the PyQt Qt DLLs rather than the PySide ones.  If you
change your PATH system variable so that the PySide directory is ahead of any
the Qt/PyQt ones do you still get the error?

Funny things also tended to occur if you happened to be doing anything that
loaded PyQt4 (like using it as the default backend).

Gerald.

Comment 2 Hugo Parente Lima 2011-03-28 21:20:26 EEST

Works for me on Linux and Python 2.6.

[hugo@thinkpadugo code (master) 4.7] $ ipython -pylab                           
Python 2.7.1 (r271:86832, Feb 21 2011, 01:28:26)                                
Type "copyright", "credits" or "license" for more information.                  

IPython 0.10.1 -- An enhanced Interactive Python.                               
?         -> Introduction and overview of IPython's features.                   
%quickref -> Quick reference.                                                   
help      -> Python's own help system.                                          
object?   -> Details about 'object'. ?object also works, ?? prints more.        

  Welcome to pylab, a matplotlib-based Python environment.                      
  For more information, type 'help(pylab)'.                                     

In [1]: import PySide                                                           

In [2]: obj = PySide.QtCore.QObject()

In [3]: obj.setObjectName("Hi")

In [4]: 
Do you really want to exit ([y]/n)? y
-------------------------------
WrapperMap: 0x2fe91e0 (size: 0)
-------------------------------

Comment 3 Hugo Parente Lima 2011-03-28 21:22:02 EEST

(In reply to comment #2)
> Works for me on Linux and Python 2.6.

Oops, I mean.. Python 2.7

Comment 4 Hugo Parente Lima 2011-03-28 21:23:42 EEST

(In reply to comment #1)
> I can do this without error.  
> 
> That DLL error looks awfully similar to one I came across that seemed to be
> caused by PySide loading the PyQt Qt DLLs rather than the PySide ones.  If you
> change your PATH system variable so that the PySide directory is ahead of any
> the Qt/PyQt ones do you still get the error?
> 
> Funny things also tended to occur if you happened to be doing anything that
> loaded PyQt4 (like using it as the default backend).
> 
> Gerald.

Could you add some info about that on PySide FAQ?

http://developer.qt.nokia.com/wiki/PySide_FAQ

Comment 5 Hugo Parente Lima 2011-04-12 17:36:34 EEST

Marking as invalid after comment #1 from Gerald, this is just an issue in the
reporter environment.

Comment 6 renato filho 2011-04-29 18:07:55 EEST

PySide release 1.0.2