Re: [PyInstaller] Re: pyinstaller interactive python console

2021-03-15 Thread Jones, Bryan 
Use Conda.

On Mon, Mar 15, 2021 at 8:39 AM Bachir Aoun  wrote:

> just fyi, what i did to solve  the need for now is to read the file and
> call exec.
> this is a patch solution hoping that there is one that is more native to
> pyinstaller.
>
> On Sunday, March 14, 2021 at 11:01:08 AM UTC-5 Bachir Aoun wrote:
>
>> Hi,
>> I am trying to create a standalone for a scientific community package.
>> Scientists are typically facing difficulties installing  and compiling the
>> package on their windows machine.
>> (they need to set python path, install visual studio compiler, etc.)
>>
>> I am trying to bundle everything in one executable, the goal is still to
>> be able to open the app and have a python terminal launched.
>>
>> here's my question on stack overflow for more info
>>
>>
>> https://stackoverflow.com/questions/66625019/pyinstaller-interactive-python-console
>>
>>
>> I appreciate any help
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pyinstaller/6d3b2380-00f1-4735-ba2b-33f5ec992df6n%40googlegroups.com
> 
> .
>


-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pyinstaller/CAHhYbD9TTercAtHGZFxS7SaY1dbS3EF7zu8q4xhw-mVk5SyYTg%40mail.gmail.com.

Re: [PyInstaller] How to prevent PyInstaller packaging unused modules

2019-11-07 Thread Jones, Bryan 
Another approach: create a venv and install only what you want packaged.

The Pyinstaller dependency analysis is conservative -- if there's a case
where package x might be needed, it will be included. It can't tell what
your use-case is.

On Thu, Nov 7, 2019 at 6:11 AM Brendan Simon (eTRIX) <
brendan.si...@etrix.com.au> wrote:

> On 7/11/2019 9:44 pm, Hartmut Goebel wrote:
>
> Am 06.11.19 um 23:35 schrieb Brendan Simon (eTRIX):
>
> Is there a way to get PyInstaller to only package the modules that the app
> will use (other than commenting out code everywhere?)
>
> pyinstaller --help is your friend.
>
> I have been through all the documents and stackoverflow.  I am using a
> spec file and have been playing with filtering out various files before
> producing the exe.  e.g. removing all the ".npy" and ".npz" data files that
> I don't need.
>
> So running `pyinstaller --help` did help me focus back on
> `--exclude-module`.  This by itself doesn't do what I want, which is for
> pyinstaller to not include modules it never sees (or what the app would
> never see if run).  Maybe that's not possible to do?
>
> Anyway using `--exclude-module` at command line would mean I need
> different scripts with different sets of command arguments (or one script
> with some settings).
>
> Thinking about it more, I could probably do it in the spec file too, by
> importing those CONFIG attributes from the app and setting the `excludes`
> list as required.
>
> I'll give that a whirl.
>
> Vielen Dank !
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pyinstaller/6fc2db98-9829-19bb-92cb-3173c0537286%40etrix.com.au
> 
> .
>


-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pyinstaller/CAHhYbD-FUKjRHtg-fkeDDDgeRgDD6Gm4i53jncK-8PQhdXgi_w%40mail.gmail.com.

Re: [PyInstaller] How to Report Bugs

2019-05-10 Thread Jones, Bryan 
Michael,

a) - github issues are correct. However, the volume of issues vs the people
who answer is to out of balance, so don't expect much.
b) - I got it.

Bryan

On Fri, May 10, 2019 at 2:42 AM Michael  wrote:

> a) a bit of feedback
>
> b) test the maillist is working
>
> re: a. - Just read through
> https://github.com/pyinstaller/pyinstaller/wiki/How-to-Report-Bugs and I
> what is hard to find is WHERE to actually post a bug. I opened two
> issues earlier this week in the "Issue" tab of the git project, but I am
> uncertain if that should have been elsewhere (e.g., CPython has an
> 'issues' site, and when a patch is available the discussion is "mixed"
> in the PR, when the focus is the patch, and in the issues when not
> directly related to specific code.
>
> I am wondering how PyInstaller manages discussions.
>
> re: b. - just going to see where this message goes, and how long before
> I see it my mailbox.
>
> Regards,
>
> Michael
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pyinstaller/993f6e84-5efa-caee-b38a-e316533c8607%40felt.demon.nl
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pyinstaller/CAHhYbD_ABfqHcP0Jgj5wNGPGcajP-zVUEkjKfxTmUw97%2BCv%2Bqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

2019-04-04 Thread Jones, Bryan 
Use the development version, which contains a fix for this.

On Thu, Apr 4, 2019 at 2:12 AM 
wrote:

> hello all,
>
> I am facing difficulties in making .exe for .py. I am getting below error.
> Error :
>
> 100 INFO: PyInstaller: 3.4
> 100 INFO: Python: 3.6.0
> 100 INFO: Platform: Windows-10-10.0.15063-SP0
> 115 INFO: UPX is not available.
> 115 INFO: Extending PYTHONPATH with paths
> ['D:\\FY_19\\On_going\\Fluent\\python',
> 'D:\\FY_19\\On_going\\Fluent\\python']
> 115 INFO: checking Analysis
> 115 INFO: Building Analysis because Analysis-00.toc is non existent
> 115 INFO: Initializing module dependency graph...
> 131 INFO: Initializing module graph hooks...
> 131 INFO: Analyzing base_library.zip ...
> 4958 INFO: running Analysis Analysis-00.toc
> 4978 INFO: Adding Microsoft.Windows.Common-Controls to dependent
> assemblies of final executable
>   required by c:\programdata\anaconda3\python.exe
> 5735 INFO: Caching module hooks...
> 5755 INFO: Analyzing Flow_field_convert.py
> 7745 INFO: Processing pre-find module path hook   distutils
> 7953 INFO: Processing pre-find module path hook   site
> 7954 INFO: site: retargeting to fake-dir
> 'c:\\programdata\\anaconda3\\lib\\site-packages\\PyInstaller\\fake-modules'
> 10632 INFO: Processing pre-safe import module hook
>  setuptools.extern.six.moves
> 20108 INFO: Processing pre-safe import module hook   six.moves
> 91760 INFO: Loading module hooks...
> 91760 INFO: Loading module hook "hook-babel.py"...
> 92010 INFO: Loading module hook "hook-boto.py"...
> 92065 INFO: Loading module hook "hook-Crypto.py"...
> Traceback (most recent call last):
>   File "", line 2, in 
> ModuleNotFoundError: No module named 'Crypto.Math'
> 92215 INFO: Loading module hook "hook-cryptography.py"...
> 93217 INFO: Loading module hook "hook-distutils.py"...
> 93217 INFO: Loading module hook "hook-docutils.py"...
> 95548 INFO: Loading module hook "hook-encodings.py"...
> 95733 INFO: Loading module hook "hook-IPython.py"...
> 95778 INFO: Excluding import 'PyQt5'
> 95785 INFO:   Removing import of PyQt5.QtSvg from module
> IPython.external.qt_loaders
> 95785 INFO:   Removing import of PyQt5 from module
> IPython.external.qt_loaders
> 95785 INFO:   Removing import of PyQt5.QtCore from module
> IPython.external.qt_loaders
> 95785 INFO:   Removing import of PyQt5.QtWidgets from module
> IPython.external.qt_loaders
> 95785 INFO:   Removing import of PyQt5.QtGui from module
> IPython.external.qt_loaders
> 95785 INFO: Excluding import 'PyQt4'
> 95800 INFO:   Removing import of PyQt4 from module
> IPython.external.qt_loaders
> 95800 INFO: Excluding import 'gtk'
> 95816 INFO: Excluding import 'tkinter'
> 95832 INFO:   Removing import of tkinter from module IPython.lib.clipboard
> 95847 INFO: Excluding import 'PySide'
> 95847 INFO:   Removing import of PySide from module
> IPython.external.qt_loaders
> 95847 INFO: Excluding import 'matplotlib'
> 95864 INFO:   Removing import of matplotlib.pylab from module
> IPython.core.pylabtools
> 95865 INFO:   Removing import of matplotlib.figure from module
> IPython.core.pylabtools
> 95865 INFO:   Removing import of matplotlib.pyplot from module
> IPython.core.pylabtools
> 95866 INFO:   Removing import of matplotlib._pylab_helpers from module
> IPython.core.pylabtools
> 95866 INFO:   Removing import of matplotlib from module
> IPython.core.pylabtools
> 95868 INFO: Loading module hook "hook-jinja2.py"...
> 95887 INFO: Loading module hook "hook-jsonschema.py"...
> 95887 INFO: Loading module hook "hook-lib2to3.py"...
> 95887 INFO: Loading module hook "hook-lxml.etree.py"...
> 95902 INFO: Loading module hook "hook-matplotlib.backends.py"...
> 96817 INFO:   Matplotlib backend "GTK": ignored
> Gtk* backend requires pygtk to be installed.
> 97408 INFO:   Matplotlib backend "GTKAgg": ignored
> Gtk* backend requires pygtk to be installed.
> 97853 INFO:   Matplotlib backend "GTKCairo": ignored
> No module named 'gtk'
> 98629 INFO:   Matplotlib backend "MacOSX": ignored
> cannot import name '_macosx'
> 99291 INFO:   Matplotlib backend "Qt4Agg": ignored
> No module named 'PyQt4'
> 99895 INFO:   Matplotlib backend "Qt5Agg": ignored
> No module named 'PyQt4'
> 100599 INFO:   Matplotlib backend "TkAgg": added
> 101279 INFO:   Matplotlib backend "WX": ignored
> Matplotlib backend_wx and backend_wxagg require wxPython >=2.8.12
> 101894 INFO:   Matplotlib backend "WXAgg": ignored
> Matplotlib backend_wx and backend_wxagg require wxPython >=2.8.12
> 102328 INFO:   Matplotlib backend "GTK3Cairo": ignored
> Gtk3 backend requires pygobject to be installed.
> 103060 INFO:   Matplotlib backend "GTK3Agg": ignored
> Gtk3 backend requires pygobject to be installed.
> 104691 INFO:   Matplotlib backend "WebAgg": added
> 106167 INFO:   Matplotlib backend "nbAgg": added
> 106673 INFO:   Matplotlib backend "agg": added
> 106993 INFO:   Matplotlib backend "cairo": ignored
> Cairo backend requires that cairocffi or pycairo is installed.
> 107321

Re: [PyInstaller] [Pyinstaller] How to save data files?

2019-02-19 Thread Jones, Bryan 
It's not a bug/problem per se, it's the design of a onefile executable: it
always unpacks into a temp directory, runs, then delete the temp dir. I'd
suggest storing the file in a persistent location instead. I doubt you want
to store it back into the packed program, since this involved modifying an
executable, which most OSes require elevated permissions / frown upon.

On Tue, Feb 19, 2019 at 9:03 AM Peter Petocz  wrote:

> Hi All,
>
> I have created an application with PyQt5 and bundled it using Pyinstaller.
> The application loads login info from a login.properties file that is
> stored in the same directory as the .py file that starts the app.
>
> As suggested here
>  I
> am modifying the path with the following function:
>
> import os, sys# Translate asset paths to useable format for PyInstaller
> def resource_path(relative_path):
>   if hasattr(sys, '_MEIPASS'):
>   return os.path.join(sys._MEIPASS, relative_path)
>   return os.path.join(os.path.abspath('.'), relative_path)
>
> What it causes, is that it creates a temporary folder called _MEIPASS,
> that contains the files, like my login.properties.
>
> In the app, I want to save the login.properties info with the following
> function:
>
> self.loginFile = resource_path('./login.properties')
> def save_login_info(self):
> config = configparser.ConfigParser()
> config.read(self.loginFile)
>
> pw = self.login_ui.password_lineEdit.text()
> un = self.login_ui.username_lineedit.text()
> token = self.login_ui.token_lineEdit.text()
> alias = self.login_ui.gmail_alias_lineedit_2.text()...
> config.set('Login', 'password', pw )
> config.set('Login', 'username', un )
> config.set('Login', 'security_token', token )
> config.set('Login', 'alias', alias)
>
> with open(self.loginFile, 'w') as loginfile:
> config.write(loginfile)
>
> print('Login info saved')
>
> So the changed login info is saved to the temporary file/folder and it is
> not saved to the 'original' file.
>
> Any ideas how to mitigate this problem?
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Change release numbering schema?

2018-08-31 Thread Jones, Bryan 
I'm ambivalent about version numbers. However, I would like to see frequent
releases of PyInstaller, instead of large releases every now and then. I
think this goes back to adopting tools to make the release process easier.

On Fri, Aug 31, 2018 at 6:06 AM Hartmut Goebel 
wrote:

> Hi all,
>
> currently PyInstaller uses a somehow semantic versioning. For example:
>
> v3.0: support for Python 3
> v3.1: Support reproducible builds, Strip paths in compiled code objects
> v3.2: main" script is now byte-compiled, docs at readthedoc, etc
> v3.3: Support for Python 3.6
>
> v3.4 will bring support for Python 3.7
>
> Now I found myself not releasing v3.4 since I tough: "This is important,
> this shall be part of 3.4".
>
> One of the reasons for rare releases is the effort for writing the NEWS
> file, see [2756] for details. Now with [3698] I'm fostering the selection
> of a release-notes tool (comments are welcome!). And there is [2837] about
> preparing towncrier (the reason 2837 already exists while the decision is
> still pending is that 2837 was created as a follow-up to 2756, while 3698
> was created when I picked up the topic again after listening to a talk at
> the EuroPython conference.)
>
> Now I wonder: If we are able to release more easily and to release more
> quickly, is the current version scheme still appropriate?
>
> Should we change to to a different version scheme based on year and month,
> like several projects already to, e.g. twisted and towncrier. pip (switched
> just recently, see [1]) and attrs are using a version based on the year
> plus release count in the year.
>
> What do you thing?
>
> [1] https://github.com/pypa/pip/blob/18.0/NEWS.rst
> [2756] https://github.com/pyinstaller/pyinstaller/issues/2756
> [2837] https://github.com/pyinstaller/pyinstaller/issues/2837
> [3698] https://github.com/pyinstaller/pyinstaller/issues/3698
> --
> Schönen Gruß
> Hartmut Goebel
> Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
> Information Security Management, Security Governance, Secure Software
> Development
>
> Goebel Consult, Landshut
> http://www.goebel-consult.de
>
> Blog:
> https://www.goe-con.de/blog/das-fass-ist-voll-grunde-linux-201asystemd2018-zu-meiden
> Kolumne:
> https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2011-11-in-troja-nichts-neues
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] How to make the test framework run a .app on OSX

2018-05-11 Thread Jones, Bryan 
I put my ideas about this in your PR.

On Thu, May 10, 2018 at 11:50 PM, Glenn Ramsey  wrote:

> Hi,
>
> I'm trying to figure out how to implement a test for PyQt5's QWebEngine on
> OSX.
>
> The following test setup generates both a 'standard' executable and a .app
> but
> the test framework runs the standard exe, which doesn't work.
>
> @importorskip('PyQt5')
> def test_PyQt5_QWebEngine(pyi_builder):
> pyi_builder.test_source(
> """
> from PyQt5.QtWidgets import QApplication
> from PyQt5.QtWebEngineWidgets import QWebEngineView
> from PyQt5.QtCore import QUrl
> app = QApplication( [] )
> view = QWebEngineView()
> view.load( QUrl( "http://www.pyinstaller.org; ) )
> view.show()
> view.page().loadFinished.connect(lambda ok: app.quit())
> app.exec_()
> """, pyi_args=['--windowed', '--osx-bundle-identifier',
> 'org.qt-project.Qt.QtWebEngineCore'])
>
>
> The .app runs if I double click it in Finder or execute it from the
> command line.
>
> How do I tell the test framework to run the .app instead of the the
> standard exe?
>
> Glenn
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] PyQt5 QWebEngine on OSX

2018-05-11 Thread Jones, Bryan 
A follow-up: the Info.plist builder is at
https://github.com/pyinstaller/pyinstaller/blob/develop/PyInstaller/building/osx.py.
Somehow, a hook would need to provide info to that.

On Fri, May 11, 2018 at 7:58 AM, Jones, Bryan <bjo...@ece.msstate.edu>
wrote:

> This would make a good issue, since I don't know the answers and some
> discussion is probably required. Would you mind creating an issue? My
> questions:
>
> 1. Can --osx-bundle-identifier=org.qt-project.Qt.QtWebEngineCore be added
> programmatically in the QtWebEngineWidgets hook?
> 2. If so, what happens if a user also sets this value? Can this be
> detected, and an error raised?
>
> Not directly related to this issue, but:
>
> 1. Should the PyQt5 hook always set NSHighResolutionCapable to True in the
> Info.plist, or would this break in some cases? See https://pyinstaller.
> readthedocs.io/en/v3.3.1/spec-files.html#spec-file-options-
> for-a-mac-os-x-bundle.
> 2. I see periodic complaints about icons not appearing in the dock, and a
> comment in https://github.com/pyinstaller/pyinstaller/blob/
> develop/PyInstaller/hooks/hook-PySide2.QtWebEngineWidgets.py saying that
> setting LSUIElement to true produces this. Is this another Info.plist
> setting that should be automatically taken care of?
>
> Again, not being a Mac person, these are all things I don't really
> understand.
>
> On Fri, May 11, 2018 at 12:07 AM, Glenn Ramsey <g...@componic.co.nz> wrote:
>
>> Hi,
>>
>> PyQt5 QWebEngine on OSX requires
>>
>> --osx-bundle-identifier=org.qt-project.Qt.QtWebEngineCore
>>
>> so that the helper program QWebEngineProcess.app can work properly.
>>
>> The only place I can see that this is documented is here:
>>
>> hooks/hook-PySide2.QtWebEngineWidgets.py
>>
>> Is it possible/practical to add it to the generated Info.plist?
>>
>> It should at least be documented somewhere. Where would be a good place?
>>
>> Glenn
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "PyInstaller" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to pyinstaller+unsubscr...@googlegroups.com.
>> To post to this group, send email to pyinstaller@googlegroups.com.
>> Visit this group at https://groups.google.com/group/pyinstaller.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Bryan A. Jones, Ph.D.
> Associate Professor
> Department of Electrical and Computer Engineering
> 231 Simrall / PO Box 9571
> Mississippi State University
> Mississippi State, MS 39762
> http://www.ece.msstate.edu/~bjones
> bjones AT ece DOT msstate DOT edu
> voice 662-325-3149
> fax 662-325-2298
>
> Our Master, Jesus Christ, is on his way. He'll show up right on
> time, his arrival guaranteed by the Blessed and Undisputed Ruler,
> High King, High God.
> - 1 Tim. 6:14b-15 (The Message)
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] PyQt5 QWebEngine on OSX

2018-05-11 Thread Jones, Bryan 
This would make a good issue, since I don't know the answers and some
discussion is probably required. Would you mind creating an issue? My
questions:

1. Can --osx-bundle-identifier=org.qt-project.Qt.QtWebEngineCore be added
programmatically in the QtWebEngineWidgets hook?
2. If so, what happens if a user also sets this value? Can this be
detected, and an error raised?

Not directly related to this issue, but:

1. Should the PyQt5 hook always set NSHighResolutionCapable to True in the
Info.plist, or would this break in some cases? See
https://pyinstaller.readthedocs.io/en/v3.3.1/spec-files.html#spec-file-options-for-a-mac-os-x-bundle
.
2. I see periodic complaints about icons not appearing in the dock, and a
comment in
https://github.com/pyinstaller/pyinstaller/blob/develop/PyInstaller/hooks/hook-PySide2.QtWebEngineWidgets.py
saying
that setting LSUIElement to true produces this. Is this another Info.plist
setting that should be automatically taken care of?

Again, not being a Mac person, these are all things I don't really
understand.

On Fri, May 11, 2018 at 12:07 AM, Glenn Ramsey  wrote:

> Hi,
>
> PyQt5 QWebEngine on OSX requires
>
> --osx-bundle-identifier=org.qt-project.Qt.QtWebEngineCore
>
> so that the helper program QWebEngineProcess.app can work properly.
>
> The only place I can see that this is documented is here:
>
> hooks/hook-PySide2.QtWebEngineWidgets.py
>
> Is it possible/practical to add it to the generated Info.plist?
>
> It should at least be documented somewhere. Where would be a good place?
>
> Glenn
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Excluding PyQt5 components

2018-05-10 Thread Jones, Bryan 
Glenn,

I don't know, unfortunately. The "new and improved" system now packages
translations and does a much better job of both finding plugins and
tracking Qt library dependencies to include everything needed. So...the
result is much larger.

Based on last few lines of
https://pyinstaller.readthedocs.io/en/v3.3.1/spec-files.html#spec-file-options-for-a-mac-os-x-bundle,
perhaps the best way (at the present) is to script the deletion of unwanted
files. You can, of course, exclude modules (
https://pyinstaller.readthedocs.io/en/v3.3.1/usage.html#what-to-bundle-where-to-search),
but this won't apply to Qt libraries, plugins, or translations.

Bryan

On Thu, May 10, 2018 at 6:03 PM, Glenn Ramsey  wrote:

> Hi,
>
> With the updated PyQt5 packager in develop I notice that I get an extra
> 80MB of
> files compared to using master.
>
> What is the recommended way of excluding PyQt5 components that are not
> required?
>
> Glenn
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] How to include QtWebEngineProcess.app?

2018-05-09 Thread Jones, Bryan 
Glenn,

I have absolutely no idea how to get QtWebEngineProcess.app to work with
Pyinstaller. I struggled with this for quite a while (see
https://github.com/pyinstaller/pyinstaller/pull/3233), but have no idea how
to make that work. Any ideas are welcome!

Bryan

On Wed, May 9, 2018 at 12:13 AM, Glenn Ramsey  wrote:

> Hi,
>
> I ran into an issue where styles weren't properly included in a frozen
> app[1].
>
> This is fixed in the develop branch, but on OSX it now doesn't package
> QtWebEngineProcess.app. This was being packaged in 3.2.1, which is the
> version I
> was using previously.
>
> What do I need to do get PyInstaller to include QtWebEngineProcess.app?
>
> FWIW I wrote the initial PyQt5 support (mostly by copying and revising the
> PyQt4
> stuff) but that code has pretty much all been improved and replaced now so
> I no
> longer know how it works.
>
> Glenn
>
> [1]
> https://stackoverflow.com/questions/48892935/pyinstaller-packaged-pyqt5-
> app-uses-wrong-style-on-macos
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi State, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Python, Windows and no console environments

2017-03-31 Thread Jones, Bryan 
Aargh, you're correct. Thanks for the catch! Fixed.

Bryan

On Thu, Mar 30, 2017 at 3:55 PM, Coyot Linden (Glenn Glazer) <
co...@lindenlab.com> wrote:

> Oh, and I found another bug in the recipe.  In:
>
> ret = {'stdout:': subprocess.PIPE}
>
> There is an extra colon inside the key.  Since subprocess doesn't know
> what 'stdout:', this causes its init() to throw a type exception.
>
> Best,
>
> coyot
>
> On 3/27/17 14:48, Jones, Bryan wrote:
>
> Thanks, fixed!
>
> On Mon, Mar 20, 2017 at 3:40 PM, Coyot Linden (Glenn Glazer) <
> co...@lindenlab.com> wrote:
>
>> On 3/20/17 12:01, Coyot Linden (Glenn Glazer) wrote:
>>
>> On 3/16/17 10:07, Jones, Bryan wrote:
>>
>> This link might be relevant -- https://github.com/pyinstal
>> ler/pyinstaller/wiki/Recipe-subprocess
>>
>> Have you tried those suggestions?
>>
>>
>> One other quick note: the recipe calls for half a pound of sugar a
>> hasattr test that sets an isFrozen variable that is actually never used in
>> the code or test code.
>>
>> Best,
>>
>> coyot
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Python, Windows and no console environments

2017-03-27 Thread Jones, Bryan 
Thanks, fixed!

On Mon, Mar 20, 2017 at 3:40 PM, Coyot Linden (Glenn Glazer) <
co...@lindenlab.com> wrote:

> On 3/20/17 12:01, Coyot Linden (Glenn Glazer) wrote:
>
> On 3/16/17 10:07, Jones, Bryan wrote:
>
> This link might be relevant -- https://github.com/
> pyinstaller/pyinstaller/wiki/Recipe-subprocess
>
> Have you tried those suggestions?
>
>
> One other quick note: the recipe calls for half a pound of sugar a
> hasattr test that sets an isFrozen variable that is actually never used in
> the code or test code.
>
> Best,
>
> coyot
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Python, Windows and no console environments

2017-03-16 Thread Jones, Bryan 
Steve,

Great idea -- thanks!

Bryan

On Thu, Mar 16, 2017 at 12:51 PM, Steve Barnes <gadgetst...@live.co.uk>
wrote:

> I have also raised an issue on the cpython manuals,
> http://bugs.python.org/issue29829, requesting a note be added to the
> subprocess documentation.
>
> Steve
>
> On 16/03/2017 17:24, Coyot Linden (Glenn Glazer) wrote:
> > No, I hadn't seen that.
> >
> > Thanks for the pointer!
> >
> > Best,
> >
> > coyot
> >
> >
> > On 3/16/17 10:07, Jones, Bryan wrote:
> >> This link might be relevant
> >> -- https://github.com/pyinstaller/pyinstaller/wiki/Recipe-subprocess
> >>
> >> Have you tried those suggestions?
> >>
> >> On Thu, Mar 16, 2017 at 10:47 AM, Coyot Linden (Glenn Glazer)
> >> <co...@lindenlab.com <mailto:co...@lindenlab.com>> wrote:
> >>
> >> We discovered that code which ran perfectly correctly by executing
> >> the scripts in the POSIX environment or via python on the Windows
> >> command prompt would fail when compiled using the -w flag to
> >> PyInstaller. This flag prevents the application from launching a
> >> console window when the application starts, which we clearly did
> >> not want with our client. The problem occurs when a caller
> >> executes Python's subprocess and the caller tries to implicitly or
> >> explictly access stderr or stdin on Windows.
> >>
> >> Because this originally occurred in our code with a caller of an
> >> imported module our test code used that mode.  We believe it can
> >> be reproduced without the caller.
> >>
> >> We also believe that this error is a deep down result in the
> >> pythonw implementation on Windows and PyInstaller just makes it
> >> more obvious.  Some trials suggest that pythonw produces the same
> >> failure cases, albeit with somewhat different output.
> >>
> >> To the PyInstaller team: we found (and is reproducible with the
> >> code in the appendices below) that even with -w, a console window
> >> flashes for a tiny fraction of a second.  Is there any way to
> >> eliminate that completely?
> >>
> >> -
> >>
> >> So beginning with code that fails that shows the example, we have:
> >>
> >> Sample problematic caller code:
> >>
> >> #!/usr/bin/env python
> >>
> >> import cgitb
> >> import os.path
> >> import subwrapper
> >> import sys
> >>
> >> cwd = os.path.dirname(os.path.realpath(str(sys.executable)))
> >> cgitb.enable(logdir=cwd, format='text')
> >>
> >> print subwrapper.getMachineID()
> >>
> >> Sample problematic imported module code:
> >>
> >> #!/usr/bin/env python
> >>
> >> import subprocess
> >>
> >> def getMachineID():
> >>return subprocess.check_output(['wmic','csproduct','get','UUID'
> ])
> >>
> >>  Sample output under python:
> >>
> >> >python caller.py
> >> UUID
> >> D8F59000-4F39---
> >>
> >> Sample output when compiled with the -y --clean --onefile flags:
> >>
> >> >caller.exe
> >> UUID
> >> D8F59000-4F39---
> >>
> >> Sample output when compiled with the -y -w --clean --onefile flags:
> >>
> >> No output.  Failure to execute script window appears (the name
> >> depends on the script name):
> >>
> >>
> >>
> >> Note that this error message is specific to PyInstaller, it comes
> >> from
> >> https://github.com/pyinstaller/pyinstaller/blob/
> a70b20e4de6a6817987d28ca9f3201c8105fd858/bootloader/src/pyi_launch.c#L411
> >> <https://github.com/pyinstaller/pyinstaller/blob/
> a70b20e4de6a6817987d28ca9f3201c8105fd858/bootloader/src/pyi_launch.c#L411>
> >> .
> >>
> >> As noted above, we ran the toy scripts under cgitb tracing to
> >> obtain detailed call stack information which does not normally
> >> appear when that Window appears.  Full cgitb output is below, but
> >> the important part is:
> >>
> >> Traceback (most recent call last):
> >>   File "caller.py", line 11, in 
> >>   File "subwrapper.py", line 6, i

Re: [PyInstaller] Python, Windows and no console environments

2017-03-16 Thread Jones, Bryan 
This link might be relevant --
https://github.com/pyinstaller/pyinstaller/wiki/Recipe-subprocess

Have you tried those suggestions?

On Thu, Mar 16, 2017 at 10:47 AM, Coyot Linden (Glenn Glazer) <
co...@lindenlab.com> wrote:

> We discovered that code which ran perfectly correctly by executing the
> scripts in the POSIX environment or via python on the Windows command
> prompt would fail when compiled using the -w flag to PyInstaller. This flag
> prevents the application from launching a console window when the
> application starts, which we clearly did not want with our client. The
> problem occurs when a caller executes Python's subprocess and the caller
> tries to implicitly or explictly access stderr or stdin on Windows.
>
> Because this originally occurred in our code with a caller of an imported
> module our test code used that mode.  We believe it can be reproduced
> without the caller.
>
> We also believe that this error is a deep down result in the pythonw
> implementation on Windows and PyInstaller just makes it more obvious.  Some
> trials suggest that pythonw produces the same failure cases, albeit with
> somewhat different output.
>
> To the PyInstaller team: we found (and is reproducible with the code in
> the appendices below) that even with -w, a console window flashes for a
> tiny fraction of a second.  Is there any way to eliminate that completely?
>
> -
>
> So beginning with code that fails that shows the example, we have:
>
> Sample problematic caller code:
>
> #!/usr/bin/env python
>
> import cgitb
> import os.path
> import subwrapper
> import sys
>
> cwd = os.path.dirname(os.path.realpath(str(sys.executable)))
> cgitb.enable(logdir=cwd, format='text')
>
> print subwrapper.getMachineID()
>
> Sample problematic imported module code:
>
> #!/usr/bin/env python
>
> import subprocess
>
> def getMachineID():
>return subprocess.check_output(['wmic','csproduct','get','UUID'])
>
>  Sample output under python:
>
> >python caller.py
> UUID
> D8F59000-4F39---
>
> Sample output when compiled with the -y --clean --onefile flags:
>
> >caller.exe
> UUID
> D8F59000-4F39---
>
> Sample output when compiled with the -y -w --clean --onefile flags:
>
> No output.  Failure to execute script window appears (the name depends on
> the script name):
>
>
>
> Note that this error message is specific to PyInstaller, it comes from
> https://github.com/pyinstaller/pyinstaller/blob/
> a70b20e4de6a6817987d28ca9f3201c8105fd858/bootloader/src/pyi_launch.c#L411
> .
>
> As noted above, we ran the toy scripts under cgitb tracing to obtain
> detailed call stack information which does not normally appear when that
> Window appears.  Full cgitb output is below, but the important part is:
>
> Traceback (most recent call last):
>   File "caller.py", line 11, in 
>   File "subwrapper.py", line 6, in getMachineID
>   File "subprocess.py", line 566, in check_output
>   File "subprocess.py", line 702, in __init__
>   File "subprocess.py", line 823, in _get_handles
> WindowsError: [Error 6] The handle is invalid
>
> Researching that error message led us to:
>
> https://github.com/incuna/django-wkhtmltopdf/issues/91#
> issuecomment-179080434
>
> which points at the problem being related to the passing of filehandles,
> but suggests hacking subprocess.py, which we were extremely reluctant to do
> for production software.
>
> We also found:
>
> http://stackoverflow.com/questions/337870/python-
> subprocess-call-fails-when-using-pythonw-exe
>
> which states
>
> *"sys.stdin and sys.stdout handles are invalid because pythonw does not
> provide console support as it runs as a deamon, so default arguments of
> subprocess.call() are failing.*
>
> *Deamon (sic) programs close stdin/stdout/stderr purposedly and use
> logging instead, so that you have to manage this yourself: I would suggest
> to use subprocess.PIPE."*
>
> The last comment at the end of that StackOverflow indicates that people
> have been running into this problem with pythonw and PyInstaller since 2014.
>
> Putting these things together, we realized that -w is destroying the
> stderr filehandle. We now do subprocess calls this way:
>
> with open(os.path.join(cwd,'output'),'a') as bar:
>with open(os.devnull) as nullin:
>try:
>foo = subprocess.check_output(['
> wmic','csproduct','get','UUID'], stdout=subprocess.PIPE,
> stderr=subprocess.PIPE, stdin=nullin)
>print >>bar, foo
>
> which is to say that we never, ever use stdin or stderr on Windows for
> anything, explicitly OR implicitly through default options.  E.g., passing
> None to check_output() for a handle or not specifying a handle causes it to
> inherit from the parent and there is nothing to inherit and hence the
> invalid handle error message.  No print statements, either.  All debugging
> must go to logs.
>
> Best,
>
> coyot
>
> Appendix A - Correct Version of caller.py
>
> #!/usr/bin/env python
>
> import cgitb
>

Re: [PyInstaller] Preparing release 3.2

2016-05-02 Thread Jones, Bryan 
Nothing from my side. I have a few more patches coming, but they're not
critical for the release.

On Sun, May 1, 2016 at 6:45 AM, Hartmut Goebel 
wrote:

> Hi,
>
> it's time to release 3.2. I can take care of it, but am unsure if I'll
> make it prior to 2016-05-11.
>
> Anything that should go into it?
>
> --
> Schönen Gruß
> Hartmut Goebel
> Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
> Information Security Management, Security Governance, Secure Software
> Development
>
> Goebel Consult, Landshut
> http://www.goebel-consult.de
>
> Blog:
> http://www.goebel-consult.de/blog/digitale-burgerrechte-in-der-ara-snowden
> Kolumne:
> http://www.cissp-gefluester.de/2011-09-kommerz-uber-recht-fdp-die-gefaellt-mir-partei
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Examples of projects using PyInstaller

2016-01-29 Thread Jones, Bryan 
A few ideas on how to do this:

> Hmm, is there a way to capture data file requirements as command-line
options?

Yes, mostly: write a hook file for your project that defines the
appropriate datas, then pass the path to your hook file on the command line.

 > It would be sweet if in the future PyInstaller could somehow reuse the
project’s MANIFEST.in for this kind of stuff.

I agree. What might make this more generalizable: write a hook utility
function (perhaps collect_manifest) that would read a MANIFEST.in and
convert that to datas in a hook file? That way, if an app depends on
several other packages which have MANIFEST.in available, all of these can
be used by pyinstaller.

Bryan

On Fri, Jan 29, 2016 at 4:22 PM, Nicholas Chammas <
nicholas.cham...@gmail.com> wrote:

> Makes sense. I’ll report back if I find there is something I need that I
> can’t do from the command line interface.
>
> Hmm, is there a way to capture data file requirements as command-line
> options?
>
> a = Analysis(
> ['my-program.py'],
> datas=[
> ('data-dir', './data-dir'),
> ('some-file', './some-file'),
> ],
>
> It doesn’t seem to be the case. Maybe in my case I need to check in my
> .spec file.
>
> (This reminds me, by the way, of my post here
> . It would be
> sweet if in the future PyInstaller could somehow reuse the project’s
> MANIFEST.in for this kind of stuff.)
>
> Nick
>
> On Thursday, January 28, 2016 at 5:36:38 PM UTC-5, Nicholas Chammas wrote:
>
> You may have a look at brog -backup: https://github.com/borgbackup/borg
>>>
>> Thanks for the reference! Looks like this is the money shot
>> 
>> .
>>
>> As long as you can pass all required parameters on the command line, I'd
>>> suggest *not* using a .spec-file. This eases updating for the case the
>>> .spec-file would change or get new features.
>>>
>> Makes sense. I’ll report back if I find there is something I need that I
>> can’t do from the command line interface.
>>
>>
>>>- Do they restructure their project in any way to better support
>>>PyInstaller?
>>>
>>> If you are using virtual environments, this should not be necessary.
>>> Just setup the virtual env, install everything required into it, an run
>>> pyinstaller.
>>>
>> Ah, in my case I had to make a small change to add a script that can be
>> called directly, like python3 my-program.py. That’s because the normal
>> way to invoke my program is via a console_scripts entry point, and 
>> PyInstaller
>> doesn’t know how to interface with that yet
>>  (as you know).
>>
>>
>>>- Do they use CI services like Travis and AppVeyor to automatically
>>>test their packaging process and generate release artifacts for the 
>>> various
>>>OSes?
>>>
>>> borg backup uses travis and Vagrant. (I personally find the later one
>>> very interesting and adopted it for building PyInstallers bootloader.)
>>>
>> Interesting. I’ll take a look at Travis first since it supports uploading
>> artifacts to S3 .
>> So I can have PyInstaller run as one of my “tests” and publish the result
>> to S3.
>>
>> Nick
>> ​
>>
> ​
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Problem building Qt app for Windows with pyinstaller

2016-01-13 Thread Jones, Bryan 
Dave,

I've built my Windows application using Py3.4 64 bit, Qt5.5, on a Windows 8
PC with no problems. What's your configuration? Have you read through
https://github.com/pyinstaller/pyinstaller/wiki/How-to-Report-Bugs?

Bryan

On Tue, Jan 12, 2016 at 6:53 PM,  wrote:

> Hi all,
>
> I've spent all day researching this and to no avail. When I try to build
> my app (in onedir mode) for Windows, I keep getting this error when I try
> to run it:
>
> "This application failed to start because it could not find or load the Qt
> platform plugin "windows".
>
> I have tried modifying my spec file, I even tried manually adding a folder
> like so:
>
> /
>dist/
>   main/
>  platforms/
> qwindows.dll <== ADDED FILE HERE
>  main.exe
>
> But the error persists. I really don't know what else to do. On OSX, this
> builds and runs just fine and in fact creates a qt5_plugins dir in my dist
> main folder.
>
> Please help!
> -Dave
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at https://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] ELI5 - python3 branch in local clone?

2015-09-10 Thread Jones, Bryan 
Personally, I'm a fan of SmartGit. It has a MUCH better and more funcitonal
GUI than git gui / gitk, and is still free for open-source projects.

On Thu, Sep 10, 2015 at 4:09 AM, Hartmut Goebel 
wrote:

> Am 08.09.2015 um 23:55 schrieb David Cortesi:
>
> I want to work on the docs and am embarrassed to run into problems with
> basic git/hub usage. I thought I knew this stuff a little bit, but I guess
> not. On Github I fork PyInstaller/PyInstaller. All four branches are
> visible. But when I try to make a local clone...
>
>
> Martin already posted the answer.
>
> Beside of this, I recommend using `git gui` and `gitk --all`, both are
> quite useful and mighty tools. I sue gitk all lot for switching branches,
> having a visual overview etc. And I'm using git gui for committing, esp.
> since one can select single files or even single lines for commit.
>
> --
> Schönen Gruß
> Hartmut Goebel
> Dipl.-Informatiker (univ), CISSP, CSSLP
> Information Security Management, Security Governance, Secure Software
> Development
>
> Goebel Consult, Landshut
> http://www.goebel-consult.de
>
> Blog: http://www.goebel-consult.de/blog/ehrlichkeit-made-in-germany
> Kolumne:
> http://www.cissp-gefluester.de/2011-08-horrorszenario-bring-your-own-device
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pyinstaller+unsubscr...@googlegroups.com.
> To post to this group, send email to pyinstaller@googlegroups.com.
> Visit this group at http://groups.google.com/group/pyinstaller.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at http://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Executable does not use additional files (config files)

2014-11-19 Thread Jones, Bryan 
Jose,

To access file relative to the frozen version of your app, take a look at;

http://htmlpreview.github.io/?https://github.com/pyinstaller/pyinstaller/blob/develop/doc/Manual.html#accessing-data-files

That will probably fix your problem.

On Thu, Nov 13, 2014 at 8:07 AM, Jose Luis Da joseluis.d...@upf.edu wrote:

 Hi all,

 I want to create a standalone executable file for a python code that uses
 two txt files (config files) which define some parameters.

 If somebody changes the parameters of those text files, the standalone
 application should take it into account, i.e., the text files do not have
 to be fixed in the final code.

 I am using PyInstaller on OS X, I create the executable file, but it does
 not read the text files, while the python code does it without problem.

 Those are the commands I use to create the executable file:

 python utils/makespec.py --onefile ../extest/exec_test.py nueye$ python
 utils
 nueye$ python utils/build.py exec_test/exec_test.spec


 What I am doing wrong? Or what should I add to my procedure?

 Thank you,
 jl

 --
 You received this message because you are subscribed to the Google Groups
 PyInstaller group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to pyinstaller+unsubscr...@googlegroups.com.
 To post to this group, send email to pyinstaller@googlegroups.com.
 Visit this group at http://groups.google.com/group/pyinstaller.
 For more options, visit https://groups.google.com/d/optout.




-- 
Bryan A. Jones, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

-- 
You received this message because you are subscribed to the Google Groups 
PyInstaller group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at http://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.