Skip to content

Problems with pyinstaller version (Linux) #835

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
RobertoBagnara opened this issue Jan 25, 2023 · 0 comments · Fixed by #838
Closed

Problems with pyinstaller version (Linux) #835

RobertoBagnara opened this issue Jan 25, 2023 · 0 comments · Fixed by #838

Comments

@RobertoBagnara
Copy link
Contributor

The following sequence of commands

$ mkdir /tmp/test
$ cd /tmp/test/
$ git clone https://github.com/strictdoc-project/strictdoc.git
$ invoke release-pyinstaller
$ /tmp/strictdoc/strictdoc/strictdoc server ./tests/unit_server/strictdoc/server/01_hello_world/sample.sdoc

results in the following error message:

******************************************
*               WARNING                  *
*                                        *
* The StrictDoc Web-based user interface *
* is a highly experimental feature.      *
* Things may go wrong, so get ready      *
* to report bugs.                        *
******************************************

WARNING:  Current configuration will not reload as not all conditions are met,please refer to documentation.
ERROR:    Error loading ASGI app. Could not import module "strictdoc.server.app".

In contrast, the server command does the right thing with a version of strictdoc obtained by pip install -U strictdoc.
In addition, the pyinstaller version seems to work for other commands, e.g.,

$ /tmp/strictdoc/strictdoc/strictdoc export ./tests/unit_server/strictdoc/server/01_hello_world/sample.sdoc

does the right thing.

See attachment for the full details.
details.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants