diff options
| author | Shyamnath Premnadh <shyamnath.premnadh@qt.io> | 2023-03-20 10:51:56 +0100 |
|---|---|---|
| committer | Shyamnath Premnadh <shyamnath.premnadh@qt.io> | 2023-03-27 09:01:18 +0100 |
| commit | 4d4f744c570d2feb79163051d2fd4c73336f1758 (patch) | |
| tree | 372f4e18fe6978d1441164352836e88f8b1647ab /examples/quickcontrols/filesystemexplorer/FileSystemModule/qml/FileSystemView.qml | |
| parent | 5529853210de3e51b2ad3c636ebee4a4d77aa54e (diff) | |
Deployment Tool: Remove create_venv + fix --dry-run/--init
- As the deployment tool's code base grows larger, I realized that
the ability to create a venv using pyside6-deploy was a bit of
over engineering. There are instances where I have to use the
current Python interpreter to fetch some information from the
newly created venv Python, which results in weird code.
Note: The tool would still work even if the user is using a
globally installed Python interpreter with PySide6 installed.
- Now, the user is warned if he is not in a virtual environment and
prompted the requirement to install further Python packages. If
the user input's "no", then the tool exits.
- dry_run used to create an empty 'pysidedeploy.spec' which can
wreck the normal deployment process. This is fixed by
pyside6-deploy using the 'default.spec' instead of creating
a new 'pysidedeploy.spec'.
Fixes: PYSIDE-2258
Task-number: PYSIDE-1612
Pick-to: 6.4 6.5
Change-Id: I376d2a6aea9f93582eab7a904a81f48426bfee18
Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'examples/quickcontrols/filesystemexplorer/FileSystemModule/qml/FileSystemView.qml')
0 files changed, 0 insertions, 0 deletions