I'm not very familiar with Django, but I recently did something
similar with PYramid.
The trick *may* be that Django is doing a bunch of its configuration/
discovery dynamically, at run time. That was the case with Pyramid --
essentially is was scanning the code at run time looking for views to
On Mon, Feb 24, 2020 at 1:34 AM JAY JAY wrote:
> Hopefully a simple question, but I can't run my app once I send it to
> someone else, or upload it and download it to my own computer:
>
> "The application X cannot be opened."
>
> Once I add chmod +x, it works! So, I'm almost there! How do I make
To pick up on my own note:
Turns out I had an unneeded dependency on numpy and scipy. I wanted to
remove that anyway, 'cause those are huge, and when I did, this
recursion issue went away.
But I do sometimes need scipy -- so it would good it could work.
I suspect that PyInstaller could be a
When running pyinstaller, it churns away for a long time, and results in an
recursion limit exceeded error.
I even cranked up the recursion limit in the spec file (as suggested
elsewhere in this list) and it took longer, but same error.
I am highly suspicious that this is an infinite recursion.
I think you need to rethink a bit what you are doing here:
You are calling a python program from within a python program? Why? Do you
need two programs running?
If you do have a good reason, then you need to rethink how you are using
PyInstaller (and maybe it's not the right tool).
PyInstaller
start it up.
Then point PyInstaller at that start up script, and presto -- a stand alone
application.
HTH,
-CHB
>
> thank you again for being kind and sharing ur thoughts!
>
> On Mon, Feb 17, 2020, 4:16 PM 'Chris Barker' via PyInstaller <
> pyinstaller@googlegroups.com> wr
it seems you've solved your issue, but a note:
My environment/install looks like this:
> conda create --name myapp python=3.7
> conda activate myapp
> conda install -c numba numba # numba is optional, actually
> conda install -c conda-forge librosa
> conda install pyqt pillow
On Fri, Mar 27, 2020 at 2:13 AM abhishek bhatta
wrote:
> I looked into that but there are too many packages that needs to be in the
> exclude list.
>
you might take a step back and try to figure out *why* PyInstller thinks
you need all those packages.
Perhaps you can do your imports
yup -- a lot of this is BIG.
numpy is 23MB on my Mac -- yours seems big -- maybe using MKL?
You may not be using all of numpy, but it's really hard to tease out what
you are really using mostly it doesn't matter: disk space is really cheap
these days. Bandwidth not always, but still, folks are
On Mon, May 11, 2020 at 1:16 AM Spooky Shadow wrote:
> I have a tool organizer written in python that opens other apps using
> subprocess.
>
This is going to to come down to the details of how exactly you do that.
I'm a little fuzzy, but the subprocess module allows you to control how
things
FWIW, I think this is a great idea -- that dir can get VERY cluttered.
But it may be a challenge, particularly on Windows, as the model for dlls
is to look for them "alongside" the exe they link to.
But maybe adding to PATH, or putting in a link or shortcut for the main.exe
file could work?
> *Question*: why the mkl libraries are not properly detected/used during
>>> runtime even if they are included in the executable?
>>>
>>
MKL does some run-time magic to detect the processor and the like, so it
may be linking in an unusual way that PyInstaller can not detect.
Adding it by hand
Just a note:
Anaconda supplies a complete Python install that is not-very-different
than the one from Python.org. And the PyInstaller that it supplies is the
same as well (modulo the version).
The one way that Anaconda IS different with regard to PyInstaller is that
it supplies compiled C
I don't think you want PyInstaller here. In fact, what you are doing is
simply writing a C++ application, Python, in this case, is being used as a
C library.
So what you need to do is bundle up your app like any C++ app, that is to
say:
* It has to be linked to the Python libs
* It has to have
Another hint:
I found the default_project.maproom template in:
MapRoom.app/Contents/Resources/maproom/templates
So maybe it's simply a.matter of getting that on the search path somehow.
But how?
Here's the error again:
No document available for {'mime': 'application/x-maproom-project-zip',
I've just got a new mac with OS-X 11.6 (still Intel).
But when I try to run a PyInstaller built application, I get this error:
No document available for {'mime': 'application/x-maproom-project-zip',
'loader': , 'uri': 'template://default_project.maproom'}
And the app won't start.
This has
On Tue, Sep 26, 2023 at 12:52 AM bwoodsend wrote:
> That sounds like a red herring. It’s specifically
> subprocess.run([sys.executable,
> ...]) that we’re interested in — any other command should run fine under
> PyInstaller.
>
indeed -- a search for "sys.executable" may find the culprit.
-CHB
On Thu, Oct 5, 2023 at 8:13 AM bwoodsend wrote:
> Ughh, I’ve seen that snippet of misinformation before on stackoverflow.
>
To be fair, "putting data files next to the executable" is a long-standing
tradition on Windows from way, way back -- though I don't think it's been
best practice for a
On Tue, Aug 30, 2022 at 1:41 PM Eric Fahlgren
wrote:
> On the other hand, you can add an (or modify the existing) argument parser
> to supply those defaults in mysite.py's main. Neither of these requires
> that you do anything to your PyInstaller spec (and I'm having a hard time
> seeing where
On Wed, Aug 24, 2022 at 11:19 PM Azeez Adeniyi
wrote:
> Been battling hard with how to use pyinstaller to convert my django
> project to one executable that runs without the console. My project
> consists of apps
Do you have more than one app? that might be a bit tricky -- or might not
-- I
The solution here isn't PyInstaller specific -- it's about Python, paths,
relative paths, adn the current working dir.
A few notes:
Python respects the "current working directory" -- if you start a script
from the comamnd line, the cwd will be teh dir you started it in. If you
start it by point
In order to be able to help, we need to know exactly what you did, and what
the result was.
How did you run PyInstaller?
What error messages are you getting?
With some more information, hopefully we can help you.
By the way:
PyPi is a system designed to distribute useful packages to other
On Fri, Feb 17, 2023 at 1:59 AM Steve Barnes wrote:
> BTW: Most python to executable converts set a FROZEN attribute but I have
> found that it is not 100% reliable hence the above.
>
Is that sys.FROZEN ?
Good to know for other things as well.
-CHB
*From:* 'Chris Barker' via Py
NOTE: I don't remember the invocation, but there should be a way to check
at runtime if the app is running as a stand-alone, and conditionally set up
logging or whatever differently.
-CHB
On Thu, Feb 16, 2023 at 8:58 AM Steve Barnes wrote:
> I have come across similar before. You probably
First of all, I would try cleaning up your conda environment.
Mixing pip and conda installs can get ugly.
You want to start from scratch, and always try to install a package from
conda first, before you install with pip.
And conda-forge can be very helpful.
NOTE: I’d try making a conda
key point -- this has nothing to do with PyInstaller -- it's an issue with
your Python code -- perhaps it came up with a different input than you had
tested on (testing things is hard!
On Sun, Jul 30, 2023 at 1:27 AM Steve Barnes wrote:
> This problem can occur when the contents of
On Tue, Aug 1, 2023 at 9:23 AM 'Jasper Harrison' via PyInstaller <
pyinstaller@googlegroups.com> wrote:
> This is almost certainly a Trojan,
To be clear, this is almost certainly a false positive, due to someone
having used PyInstaller to distribute a Trojan.
> as unfortunately many amateur
I have no idea, but some debugging hints:
1) how are you running it from the terminal? If you aren't alreadyk, try:
open TheApp.app
Then you *may* get the failure, and if so, hopefully some output on the
console.
2) Open the Console App:
/System/Applications/Utilities/Console.app
Then try to
On Fri, Jan 5, 2024 at 9:34 AM Tony Cappellini wrote:
> >>But what does the second line of PyInstaller’s build log say?
> 483 INFO: PyInstaller: 6.3.0
> 483 INFO: Python: 3.11.2
>
That looks right then.
I'm no expert, but it seems something is going fundamentally wrong here. My
suggestion:
-
you've fallen into a all too common trap -- more than one Pythn
installed in your system.
decide which one you what to use, and ideall uninstall the other so you
don't have this issue again :-) -- otherwise:
figure out how to run:
python
and
pip
so that they are using the same Python.
then
On Fri, Jan 26, 2024 at 10:23 AM bruno D wrote:
> i am on an 2,4 GHz Intel Core i9 8 core .
with both OS versions? so that's not it.
> i think about a mismatch between install python-dev (with shared framework
> option ) with brew and install python 8.3.7 with pyenv
>
That would do it -- I
Not sure if this has anything to do with it, but the Mac has the additional
complication of the new M processors -- so you need to make sure you are
building a app with the right processor -- I think the recent Python.,org
builds have both built it, but you'll need to make sure.
Sorry -- I
32 matches
Mail list logo
