ducktools-env 0.2.2__tar.gz → 0.2.3__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (74) hide show
  1. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/PKG-INFO +6 -6
  2. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/README.md +5 -5
  3. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/__main__.py +1 -1
  4. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/_run.py +1 -1
  5. ducktools_env-0.2.3/src/ducktools/env/_version.py +2 -0
  6. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/scripts/get_pip.py +10 -10
  7. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools_env.egg-info/PKG-INFO +6 -6
  8. ducktools_env-0.2.2/src/ducktools/env/_version.py +0 -2
  9. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/.github/dependabot.yml +0 -0
  10. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/.github/workflows/auto_test.yml +0 -0
  11. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/.github/workflows/build_zipapp.yml +0 -0
  12. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/.github/workflows/publish_to_pypi.yml +0 -0
  13. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/.github/workflows/publish_to_testpypi.yml +0 -0
  14. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/.gitignore +0 -0
  15. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/LICENSE +0 -0
  16. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/examples/application/cowsay_app.py +0 -0
  17. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/examples/inline/cowsay_ex.py +0 -0
  18. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/examples/inline/empty_311_env.py +0 -0
  19. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/examples/inline/empty_312_env.py +0 -0
  20. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/examples/inline/pep_723_example.py +0 -0
  21. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/examples/inline/print_environment_variables.py +0 -0
  22. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/pyproject.toml +0 -0
  23. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/setup.cfg +0 -0
  24. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/__init__.py +0 -0
  25. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/_lazy_imports.py +0 -0
  26. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/_logger.py +0 -0
  27. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/_sqlclasses.py +0 -0
  28. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/bootstrapping/bootstrap.py +0 -0
  29. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/bootstrapping/bundle_main.py +0 -0
  30. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/bootstrapping/version_check.py +0 -0
  31. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/bootstrapping/zipapp_main.py +0 -0
  32. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/bundle.py +0 -0
  33. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/bundled_data.py +0 -0
  34. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/catalogue.py +0 -0
  35. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/config.py +0 -0
  36. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/environment_specs.py +0 -0
  37. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/exceptions.py +0 -0
  38. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/manager.py +0 -0
  39. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/platform_paths.py +0 -0
  40. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/register.py +0 -0
  41. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/scripts/__init__.py +0 -0
  42. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/scripts/create_zipapp.py +0 -0
  43. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools/env/scripts/get_uv.py +0 -0
  44. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools_env.egg-info/SOURCES.txt +0 -0
  45. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools_env.egg-info/dependency_links.txt +0 -0
  46. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools_env.egg-info/entry_points.txt +0 -0
  47. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools_env.egg-info/requires.txt +0 -0
  48. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/src/ducktools_env.egg-info/top_level.txt +0 -0
  49. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/conftest.py +0 -0
  50. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/data/pip-24.1.pyz +0 -0
  51. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/data/pip-24.2.pyz +0 -0
  52. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/data/uv_python_versions_list.txt +0 -0
  53. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/cowsay_app.py +0 -0
  54. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/cowsay_app.py.lock +0 -0
  55. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/cowsay_ex.py +0 -0
  56. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/cowsay_ex.py.lock +0 -0
  57. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/cowsay_ex_nolock.py +0 -0
  58. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/invalid_app.py +0 -0
  59. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/pep_723_example.py +0 -0
  60. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/pep_723_example_subset.py +0 -0
  61. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/print_environment_variables.py +0 -0
  62. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/example_scripts/spec_error.py +0 -0
  63. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_bundled_data.py +0 -0
  64. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_catalogue.py +0 -0
  65. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_config.py +0 -0
  66. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_environmentspec.py +0 -0
  67. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_fixtures_active.py +0 -0
  68. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_get_pip.py +0 -0
  69. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_get_uv.py +0 -0
  70. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_integration/test_build_retrieve.py +0 -0
  71. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_logger.py +0 -0
  72. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_manager.py +0 -0
  73. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_platform_paths.py +0 -0
  74. {ducktools_env-0.2.2 → ducktools_env-0.2.3}/tests/test_register.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: ducktools-env
3
- Version: 0.2.2
3
+ Version: 0.2.3
4
4
  Summary: Virtual environment management tools and application bundle builder
5
5
  Author: David C Ellis
6
6
  Classifier: Development Status :: 2 - Pre-Alpha
@@ -47,19 +47,19 @@ can define its own requirements.
47
47
  However, using this format requires the use of an extra package such as 'UV' or 'hatch'
48
48
  using a specific command such as `uv run my_script.py` or `hatch run my_script.py`.
49
49
 
50
- `ducktools.env` is designed to bundle your script into a Python
50
+ `ducktools-env` is designed to bundle your script into a Python
51
51
  [zipapp](https://docs.python.org/3/library/zipapp.html) which can be run by any
52
52
  Python 3.10+ install and will handle creating the virtualenv and launching the script
53
53
  with the appropriate dependencies *without* needing the other user to have any
54
54
  specific script running tool installed.
55
55
 
56
- To aid this, `ducktools.env` provides the `bundle` and `run` commands.
56
+ To aid this, `ducktools-env` provides the `bundle` and `run` commands.
57
57
 
58
- `ducktools.pyz run my_script.py`
58
+ `ducktools-env run my_script.py`
59
59
 
60
60
  Will run your script much like some of the other script runners.
61
61
 
62
- `ducktools.pyz bundle my_script.py`
62
+ `ducktools-env bundle my_script.py`
63
63
 
64
64
  Will then generate a zipapp bundle of your script and the required tools to extract and
65
65
  execute it in the same way as it is executed via the `run` command.
@@ -106,7 +106,7 @@ The tool can be used in multiple ways:
106
106
  * Accessed directly via `uvx` with uv
107
107
  * `uvx ducktools-env <command>`
108
108
 
109
- These examples will use the ducktools-env as the base as if installed via `uv tool` or a similar tool.
109
+ These examples will use the `ducktools-env` command as the base as if installed via `uv tool` or a similar tool.
110
110
 
111
111
  Run a script that uses inline script metadata:
112
112
 
@@ -20,19 +20,19 @@ can define its own requirements.
20
20
  However, using this format requires the use of an extra package such as 'UV' or 'hatch'
21
21
  using a specific command such as `uv run my_script.py` or `hatch run my_script.py`.
22
22
 
23
- `ducktools.env` is designed to bundle your script into a Python
23
+ `ducktools-env` is designed to bundle your script into a Python
24
24
  [zipapp](https://docs.python.org/3/library/zipapp.html) which can be run by any
25
25
  Python 3.10+ install and will handle creating the virtualenv and launching the script
26
26
  with the appropriate dependencies *without* needing the other user to have any
27
27
  specific script running tool installed.
28
28
 
29
- To aid this, `ducktools.env` provides the `bundle` and `run` commands.
29
+ To aid this, `ducktools-env` provides the `bundle` and `run` commands.
30
30
 
31
- `ducktools.pyz run my_script.py`
31
+ `ducktools-env run my_script.py`
32
32
 
33
33
  Will run your script much like some of the other script runners.
34
34
 
35
- `ducktools.pyz bundle my_script.py`
35
+ `ducktools-env bundle my_script.py`
36
36
 
37
37
  Will then generate a zipapp bundle of your script and the required tools to extract and
38
38
  execute it in the same way as it is executed via the `run` command.
@@ -79,7 +79,7 @@ The tool can be used in multiple ways:
79
79
  * Accessed directly via `uvx` with uv
80
80
  * `uvx ducktools-env <command>`
81
81
 
82
- These examples will use the ducktools-env as the base as if installed via `uv tool` or a similar tool.
82
+ These examples will use the `ducktools-env` command as the base as if installed via `uv tool` or a similar tool.
83
83
 
84
84
  Run a script that uses inline script metadata:
85
85
 
@@ -308,7 +308,7 @@ def main():
308
308
  if args.command == "run":
309
309
  # Split on existence of the command as a file, if the file exists run it
310
310
  # Otherwise look for it in the registered scripts database
311
- if os.path.exists(args.script_filename):
311
+ if os.path.isfile(args.script_filename):
312
312
  manager.run_script(
313
313
  script_path=args.script_filename,
314
314
  script_args=args.script_args,
@@ -43,7 +43,7 @@ def run():
43
43
 
44
44
  manager = Manager(PROJECT_NAME)
45
45
 
46
- if os.path.exists(app):
46
+ if os.path.isfile(app):
47
47
  manager.run_script(
48
48
  script_path=app,
49
49
  script_args=args,
@@ -0,0 +1,2 @@
1
+ __version__ = "0.2.3"
2
+ __version_tuple__ = (0, 2, 3)
@@ -62,21 +62,21 @@ class PipZipapp:
62
62
 
63
63
  # This is mostly kept for testing.
64
64
  PREVIOUS_PIP = PipZipapp(
65
- version_str="24.1",
66
- sha3_256="f4c4d76e70498762832a842d5b55e9d8c09b6d6607b30b5f4eb08e68dfc57077",
67
- source_url="zipapp/pip-24.1.pyz"
68
- )
69
-
70
- LATEST_PIP = PipZipapp(
71
65
  version_str="24.2",
72
66
  sha3_256="8dc4860613c47cb2e5e55c7e1ecf4046abe18edca083073d51f1720011bed6ea",
73
67
  source_url="zipapp/pip-24.2.pyz",
74
68
  )
75
69
 
70
+ LATEST_PIP = PipZipapp(
71
+ version_str="24.3.1",
72
+ sha3_256="6dd95ab685d00abada578f2744f2b235faf5876d3f3468f0756e2b78bce050f1",
73
+ source_url="zipapp/pip-24.3.1.pyz"
74
+ )
75
+
76
76
 
77
77
  def is_pip_outdated(
78
- paths: ManagedPaths,
79
- latest_version: PipZipapp = LATEST_PIP
78
+ paths: ManagedPaths,
79
+ latest_version: PipZipapp = LATEST_PIP
80
80
  ):
81
81
  pip_version = paths.get_pip_version()
82
82
 
@@ -95,8 +95,8 @@ def is_pip_outdated(
95
95
 
96
96
 
97
97
  def download_pip(
98
- pip_destination: str,
99
- latest_version: PipZipapp = LATEST_PIP
98
+ pip_destination: str,
99
+ latest_version: PipZipapp = LATEST_PIP
100
100
  ):
101
101
 
102
102
  url = latest_version.full_url
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: ducktools-env
3
- Version: 0.2.2
3
+ Version: 0.2.3
4
4
  Summary: Virtual environment management tools and application bundle builder
5
5
  Author: David C Ellis
6
6
  Classifier: Development Status :: 2 - Pre-Alpha
@@ -47,19 +47,19 @@ can define its own requirements.
47
47
  However, using this format requires the use of an extra package such as 'UV' or 'hatch'
48
48
  using a specific command such as `uv run my_script.py` or `hatch run my_script.py`.
49
49
 
50
- `ducktools.env` is designed to bundle your script into a Python
50
+ `ducktools-env` is designed to bundle your script into a Python
51
51
  [zipapp](https://docs.python.org/3/library/zipapp.html) which can be run by any
52
52
  Python 3.10+ install and will handle creating the virtualenv and launching the script
53
53
  with the appropriate dependencies *without* needing the other user to have any
54
54
  specific script running tool installed.
55
55
 
56
- To aid this, `ducktools.env` provides the `bundle` and `run` commands.
56
+ To aid this, `ducktools-env` provides the `bundle` and `run` commands.
57
57
 
58
- `ducktools.pyz run my_script.py`
58
+ `ducktools-env run my_script.py`
59
59
 
60
60
  Will run your script much like some of the other script runners.
61
61
 
62
- `ducktools.pyz bundle my_script.py`
62
+ `ducktools-env bundle my_script.py`
63
63
 
64
64
  Will then generate a zipapp bundle of your script and the required tools to extract and
65
65
  execute it in the same way as it is executed via the `run` command.
@@ -106,7 +106,7 @@ The tool can be used in multiple ways:
106
106
  * Accessed directly via `uvx` with uv
107
107
  * `uvx ducktools-env <command>`
108
108
 
109
- These examples will use the ducktools-env as the base as if installed via `uv tool` or a similar tool.
109
+ These examples will use the `ducktools-env` command as the base as if installed via `uv tool` or a similar tool.
110
110
 
111
111
  Run a script that uses inline script metadata:
112
112
 
@@ -1,2 +0,0 @@
1
- __version__ = "0.2.2"
2
- __version_tuple__ = (0, 2, 2)
File without changes
File without changes
File without changes