#test.py
import pyqtgraph as pg
print 'Hello World'
python utils/Makespec.py --console --onedir test.py
pyinstaller.py test\test.spec
I was wondering if you have worked on pyinstaller compatibility at all? Actually I dont care if it is pyinstaller or some other method for packaging python files but I would like to be able to distribute a contained file so other people could use the program. Has anyone successfully done this? My attempts at pyinstaller have been futile.
--
-- [ You are subscribed to pyqt...@googlegroups.com. To unsubscribe, send email to pyqtgraph+...@googlegroups.com ]
---
You received this message because you are subscribed to the Google Groups "pyqtgraph" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyqtgraph+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
great thanks for the document. I notice it doesnt mention the opengl part of pyqtgraph, before i get too far into it do you know if that will cause problems or not?
--
It has been a while since I worked on this, but I recently came back to it and noticed that the changelog mentions that 0.9.9 will abandon the dynamic import system. Figuring this might help, I cloned the latest development code from github and installed it. Unfortunately, once installed, it didn't work (when I imported pyqtgraph, I got a never ending string of errors). I'm not really sure what's going on there, and since it was a development version anyway I figured I'd drop it and went back and installed 0.9.8 (using python setup.py install). Out of curiosity, I tried pyinstaller anyway (because v2.1 had been released since I last tried it) and to my surprise, it worked fine! Now if I completely wipe out pyqtgraph and install 0.9.8 from scratch, it doesn't work (throws errors in frozenSupport.listdir).It is awesome that I was able to get it to work and I've already distributed my application to some co-workers who don't have python installed. However, my question is this: What is it about installing 0.9.8 over the development code that allowed this to work? I just want to make sure I'll be able to re-create it in the future...
Hah, I have no idea :)Generally installing multiple versions on top of each other is bad news. Let's focus on what was wrong with the develop branch--this has been quite stable for me and it would be great to have proper pyinstaller support for 0.9.9.
Not being an expert with such things, I assumed that running setup.py install would overwrite existing installs... obviously wrong.
That being said, troubleshooting what is wrong with my install of the develop branch is difficult because the python console literally cycles endlessly and I can't really get a grasp of what it's doing. I was able to catch a screenshot, attached below. This is using python 2.7.2 (and after realizing how far behind I was, 2.7.6). Do you have any thoughts?
This appears to be a git checkout, but an error occurred while attempting to determine a version string for the current commit.Traceback (most recent call last): File "tools\setupHelpers.py", line 103, in getVersionStrings gitVersion = getGitVersion(tagPrefix='pyqtgraph-') File "tools\setupHelpers.py", line 50, in getGitVersion tagNames = check_output(['git', 'tag'], universal_newlines=True).strip().split('\n') File "C:\Python27\lib\subprocess.py", line 566, in check_output process = Popen(stdout=PIPE, *popenargs, **kwargs) File "C:\Python27\lib\subprocess.py", line 709, in __init__ errread, errwrite) File "C:\Python27\lib\subprocess.py", line 957, in _execute_child startupinfo)WindowsError: [Error 2] The system cannot find the file specified
running install
.
.
.
I'm not sure I fully understood your other instructions. I checked out the version you suggested. Running python examples/ worked. Then I checked out develop, python examples/ still worked. I tried deleting pyqtgraph.....egg from site-packages and re-installing from both checkouts (python setup.py install from the repo directory) and both still produced the same error on import.
At the risk of derailing this thread, what was the reasoning behind abandoning the dynamic imports? This was probably a relatively large change. So, I assume there was a big motivator behind it.I haven't ever used dynamic imports in a large project. So, I'd love to hear the pros and cons just for my own education.
--
You received this message because you are subscribed to a topic in the Google Groups "pyqtgraph" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pyqtgraph/kgOhk3C91xQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pyqtgraph+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CACZXET9m6uUh2qdetqtEf5LRG%2Bdqg9D%2ByE7wue%2Bq6kAf-mERNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Interesting.. so you only get the error for installed versions of the package??The error comes from this: https://code.google.com/p/colorama/issues/detail?id=47The commit I had you check out was the one immediately before colorama was added to the library, so that should have fixed it; perhaps there were still files lingering from the previous install?
Try the following, if you don't mind:1. Make a clean install from the latest develop branch2. Download this file: https://colorama.googlecode.com/issues/attachment?aid=470001000&name=win32.py&token=jRG3YVsrkvIQA34_qx-oOLBBXjM%3A13957157087213. Move it to your installed pyqtgraph/debug/colorama/ folder (not the source folder, but the one under C:\python27\lib\site-packages or similar)4. Let me know it it helps :)
Yep, that's what I meant :)Thanks for testing this! I'll include it shortly..