haluhak149 / pythonxy

Automatically exported from code.google.com/p/pythonxy
0 stars 0 forks source link

Veusz: qtloops/sip module dependencies #620

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Recently I replaced pythonxy version 2.7.2.3 with 2.7.3.1, which updated Veusz 
1.15 => Veusz 1.16-1. After the update, Veusz refused to start. A console 
window flickered by but nothing else gave an indication it was failing. 
Eventually I got this traceback using python to launch Veusz manually:

    Traceback (most recent call last):
      File "veusz-script.pyw", line 9, in <module>
        load_entry_point('veusz==1.16', 'gui_scripts', 'veusz')()
      File "C:\Python27\lib\site-packages\pkg_resources.py", line 337, in load_entry_point
        return get_distribution(dist).load_entry_point(group, name)
      File "C:\Python27\lib\site-packages\pkg_resources.py", line 2311, in load_entry_point
        return ep.load()
      File "C:\Python27\lib\site-packages\pkg_resources.py", line 2017, in load
        entry = __import__(self.module_name, globals(),globals(), ['__name__'])
      File "C:\Python27\lib\site-packages\veusz\veusz_main.py", line 41, in <module>
        import veusz.utils as utils
      File "C:\Python27\lib\site-packages\veusz\utils\__init__.py", line 22, in <module>
        from textrender import Renderer, FontMetrics
      File "C:\Python27\lib\site-packages\veusz\utils\textrender.py", line 30, in <module>
        import points
      File "C:\Python27\lib\site-packages\veusz\utils\points.py", line 25, in <module>
        from veusz.helpers.qtloops import plotPathsToPainter
    RuntimeError: the sip module implements API v9.0 to v9.1 but the qtloops module requires API v8.1

If we trust this commendably informative runtime error message, then it appears 
the sip module was updated and qtloops module can no longer run. 

I filed this issue with pythonxy in the off-chance the sip and qtloops modules 
are packaged at the pythonxy level. I realize it's more likely to be an issue 
with Veusz itself; a duplicate of this ticket has been filed here: 
https://github.com/jeremysanders/veusz/issues/30

1. What version of Python(x,y) have you installed?
I've reverted to 2.7.2.3 since Veusz is not functional for me in 2.7.3.

b. Have you selected the "Full" component selection? <= Yes

3. Have you selected the option "Customize installation directories"?
a. Yes
5. Where did you install Python(x,y) itself? C:\pythonxy

6. Have you installed Python(x,y):  b. For "All users"

7. What is your operating system?
    a. Windows XP x64 SP2

9. When you installed Python(x,y), were you logged in as :
b. an administrator of the machine

11. Regarding installed software on your machine, how did you clean your
machine before installing Python(x,y)  (multiple answers are possible):
b. you uninstalled any previous Python distribution (including the
official .msi)
d. you cleaned the environment variables by removing all deprecated
entries

What steps will reproduce the problem? Well, at least on my box,
1. Install pythonxy 2.7.3.1 
2. Launch Veusz

What is the expected output? The application opens and awaits user input.

What do you see instead? A flicker of console window before nothing.

Original issue reported on code.google.com by wsu...@gmail.com on 15 Mar 2013 at 9:08

GoogleCodeExporter commented 9 years ago
Have you updated PyQt as well?

Original comment by grizzly.nyo on 15 Mar 2013 at 9:50

GoogleCodeExporter commented 9 years ago
I used the full installer and did not update any of the components separately 
(though I do expect PyQT would have been updated in 2.7.3.1 vs 2.7.2.3). 

Original comment by wsu...@gmail.com on 15 Mar 2013 at 11:11

GoogleCodeExporter commented 9 years ago
update Veuz with http://pythonxy.googlecode.com/files/veusz-1.16-1_py27.exe

and report the results

Original comment by grizzly.nyo on 16 Mar 2013 at 7:51

GoogleCodeExporter commented 9 years ago
OK I have good results to share but first:

While doing full un/reinstalls back and forth between Python(x,y) 2.7.2.3 and 
2.7.3.1, I encountered some odd issues. First, all the packages bundled with 
pythonxy suddenly appeared in the Add/Remove Programs list as individual 
entities. Removing pythonxy did not remove those entries. However, attempting 
to manually remove an entry resulted in Windows stating the program is no 
longer installed and offering to remove it from the list. The second oddity is 
that once this started happening, the start menu entry generated by pythonxy 
setup no longer contained links to bundled packages (gnuplot, mayavi 2, Veusz, 
etc). The shortcuts were missing regardless of whether 2.7.2.3 or 2.7.3.1 was 
installed. It looks the author of the Google Groups post "Python(x,y) Launcher 
Missing Applications and Plugins - partial workaround" [ 
https://groups.google.com/forum/?fromgroups=#!topic/pythonxy/IDSj72gFWIo ] had 
similar experience. Between un/reinstalls, I deleted the program directories 
and removed python from the path. That wasn't enough though: it wasn't until I 
removed every single reference to "Python27" from the system registry that 
normal installation and add/remove list behavior returned. 

So back to Veusz specifically... with pythonxy 2.7.3.1 out of the box, Veusz 
will not start nor give an error message. Running "python 
C:\Python27\Scripts\veusz-script.pyw" produces the same traceback as above. 
Once I install the separate plugin from the link in comment 3, Veusz launches 
and operates normally. Thanks grizzly.nyo

It's not likely the shortcuts/add-remove dialog issue is related to this as 
it's tied to the registry somehow. Should another issue be opened with those 
details? I'm not sure I could replicate the issue but it's apparently not 
limited to my experience. 

Original comment by wsu...@gmail.com on 19 Mar 2013 at 12:04

GoogleCodeExporter commented 9 years ago
Versions prior to 2.7.3.x had issues with install/uninstall. This is something 
which should have been resolved with 2.7.3.1+. Unfortunately this does not help 
older installations ...

Original comment by grizzly.nyo on 19 Mar 2013 at 6:42

GoogleCodeExporter commented 9 years ago
No it doesn't help; probably not worth a new issue. 

* For those dropping in, the Veusz dependencies can be fixed by installing the 
standalone plugin linked in comment 3.

Original comment by wsu...@gmail.com on 19 Mar 2013 at 4:00

GoogleCodeExporter commented 9 years ago

Original comment by grizzly.nyo on 20 Mar 2013 at 5:29