pyside6-deploy FileNotFoundError: [WinError 206] The filename or extension is too long

JonB

@martinbrader said in pyside6-deploy FileNotFoundError: [WinError 206] The filename or extension is too long:

File "E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial6_checker.venv\Lib\site-packages\PySide6\scripts\deploy\commands.py", line 17, in run_command
FileNotFoundError: [WinError 206] The filename or extension is too long

The error message implies to me that somewhere a filename is being generated, perhaps below this path, and you are running into a path which exceeds your Windows limits, for some call being made?

Although you may not wish to, if you installed to a path shorter than E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial6_checker.venv at the start does the error go away?

martinbrader

I forgot to mention that I am using Python 3.11
On further investigation I get this message from Nuitka:
Nuitka:WARNING: The version '3.11' is not currently supported. Expect problems.
FATAL: The Python version '3.11' is not supported by '1.2.6', but an upcoming release will add it.

martinbrader

I ran the test again this time using Python 3.10 and still got same error:
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1440, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 206] The filename or extension is too long

jsulm

@martinbrader As @JonB wrote: check what file name causes this error. The error message is quite clear about the issue.

martinbrader

@jsulm The file name is generated by the Qt provided pyside6-deploy, so I am not sure what I should do to overcome this error?

jsulm

@martinbrader Can you post the file name/path?

martinbrader

@jsulm I assume the filename is generated by pyside6-deploy but I do not know how to find out what it is. When I look inside their Python code it isn't clear to me where the filename is generated.

jsulm

@martinbrader said in pyside6-deploy FileNotFoundError: [WinError 206] The filename or extension is too long:

but I do not know how to find out what it is

Isn't it printed along the error message?

Shyamnath

How does your "pyside6-deploy" command look like? When you run it for the first time, it will generate a pysidedeploy.spec file inside the project. Can you change "--quiet" to "--verbose" for the "extra_args" field. so that you get more information on the error

martinbrader

@Shyamnath I changed the spec file as you suggested, but it doesn't seem to output any more clues?
here is how I amended pyside-deploy.spec:

[nuitka]
# (str) specify any extra nuitka arguments
# eg = extra_args = --show-modules --follow-stdlib
extra_args = --verbose

and this was the console output:
(.venv) PS E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7> pyside6-deploy.exe
Using existing config file E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\pysidedeploy.spec
[DEPLOY] Installing dependencies

Requirement already satisfied: nuitka in e:\martin\mydocs\data\python\trials_v2\dhfs_problem\trial7.venv\lib\site-packages (1.2.6)
Collecting nuitka
Downloading Nuitka-1.2.7.tar.gz (4.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.0/4.0 MB 3.1 MB/s eta 0:00:00
Preparing metadata (setup.py) ... done
Installing collected packages: nuitka
Attempting uninstall: nuitka
Found existing installation: Nuitka 1.2.6
Uninstalling Nuitka-1.2.6:
Successfully uninstalled Nuitka-1.2.6
DEPRECATION: nuitka is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change.
A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for nuitka ... done
Successfully installed nuitka-1.2.7
Requirement already satisfied: ordered_set in e:\martin\mydocs\data\python\trials_v2\dhfs_problem\trial7.venv\lib\site-packages (4.1.0)
Requirement already satisfied: zstandard in e:\martin\mydocs\data\python\trials_v2\dhfs_problem\trial7.venv\lib\site-packages (0.19.0)
[DEPLOY] Deploying application
[DEPLOY] Running Nuitka
ERROR:root:[DEPLOY]: None not found
Traceback (most recent call last):
File "E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7.venv\Lib\site-packages\PySide6\scripts\deploy\commands.py", line 17, in run_command
subprocess.check_call(command, shell=(sys.platform == "win32"))
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 364, in check_call
retcode = call(*popenargs, **kwargs)
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 345, in call
with Popen(*popenargs, **kwargs) as p:
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 971, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1440, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 206] The filename or extension is too long
Exception occurred: Traceback (most recent call last):
File "E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7.venv\Lib\site-packages\PySide6\scripts\deploy.py", line 175, in <module>
python.create_executable(
File "E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7.venv\Lib\site-packages\PySide6\scripts\deploy\python_helper.py", line 77, in create_executable
self.nuitka.create_executable(
File "E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7.venv\Lib\site-packages\PySide6\scripts\deploy\nuitka_helper.py", line 51, in create_executable
run_command(command=command, dry_run=dry_run)
File "E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7.venv\Lib\site-packages\PySide6\scripts\deploy\commands.py", line 17, in run_command
subprocess.check_call(command, shell=(sys.platform == "win32"))
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 364, in check_call
retcode = call(*popenargs, **kwargs)
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 345, in call
with Popen(*popenargs, **kwargs) as p:
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 971, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\Martin\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1440, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 206] The filename or extension is too long

jsulm

@martinbrader said in pyside6-deploy FileNotFoundError: [WinError 206] The filename or extension is too long:

pyside6-deploy.exe

I never used it, but maybe there is a way to get more verbose output from it (often -v parameter is used for that)?

Shyamnath

@martinbrader Can you please do a "pyside6-deploy --dry-run", so that i see what Nuitka command is being run

pyside6-deploy is basically a wrapper around Nuitka. I think this might be a Nuitka error. I would know for sure from the command being run.

JonB

@martinbrader
First you should do as @Shyamnath asks.

Just an observation which might help. Immediately before the "Traceback" the output shows

ERROR:root:[DEPLOY]: None not found

None is the Python keyword for a "null"/no value. I think you will find the script is not expecting something to be None at this point, indicating it has already gone wrong. If you can discover what it is that is returning None when it should be returning something else (a filepath here?) that might show what the problem is. Don't know whether this might help.

martinbrader

@Shyamnath I ran pyside6-deploy.exe --dry-run as you suggested.
The output is too large for a single post.
It consists of two lines, the second of which is 101917 chars long.
Here is the first line and around the first 1,000 chars of line 2.
NB the rest of line 2 is just more of the same with different paths:

Using existing config file E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\pysidedeploy.spec
E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\.venv\Scripts\python.exe -m nuitka E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\main.py --follow-imports --onefile --enable-plugin=pyside6 --output-dir=E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\deployment --verbose --include-qt-plugins=all --include-data-files=E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\.venv\Lib\site-packages\PySide6\examples\qml\editingmodel\main.qml=./main.qml --include-data-files=E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\.venv\Lib\site-packages\PySide6\examples\qml\editingmodel\MovingRectangle.qml=./MovingRectangle.qml --include-data-files=E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\.venv\Lib\site-packages\PySide6\examples\qml\referenceexamples\adding\example.qml=./example.qml --include-data-files=E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\.venv\Lib\site-packages\PySide6\examples\qml\referenceexamples\attached\example.qml=./example.qml --include-data-files=E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial7\.venv\Lib\site-packages\PySide6\examples\qml\referenceexamples\binding\example.qml=./example.qml

JonB

@martinbrader
@JonB said in pyside6-deploy FileNotFoundError: [WinError 206] The filename or extension is too long:

Although you may not wish to, if you installed to a path shorter than E:\Martin\MyDocs\Data\Python\Trials_v2\DHFS_problem\Trial6_checker.venv at the start does the error go away?

Did you think this might be worth giving a try?

martinbrader

@JonB Yes I reinstalled in d:\Trial9 and got same error!

Shyamnath

@martinbrader hmm, the command being run looks correct to me. Can you try running the example from the "editingmodel" folder? If that does not work, can you report a bug with the "--dry-run" ouput and I can take a look at whats wrong

Here is how you could report a bug: https://wiki.qt.io/Qt_for_Python/Reporting_Bugs

martinbrader

@Shyamnath I'm afraid same error as before when I tried with:
.venv\Lib\site-packages\PySide6\examples\gui\analogclock.main.py.

Reported bug here:
https://bugreports.qt.io/browse/PYSIDE-2164