sinoroc
For context, I am coming from here: * https://github.com/python-poetry/poetry/issues/34#issuecomment-726013631 In short, we are trying to figure out how to add _editable_ installations of some external libraries into a _poetry_-managed environment....
When running from a Zip file (`zipapp`, `*.pyz`), loading resources from package data can not be done by directly reading files relative to `__file__`, since there is no valid path...
(_yapf 0.30.0_) I would like the following code to stay as-is, i.e. the arguments (and the condition) should be indented by 8 spaces, but _yapf_ indents them with 4 spaces....
Issue was originally filed for _CPython_ here: * https://bugs.python.org/issue38145 > In the 'distutils' command 'bdist_dumb', the short option 'd' is used > for both the 'bdist-dir' and 'dist-dir' options. >...
```python extlinks = { # ... "pypi": ("https://pypi.org/project/%s", "%s"), } ``` I think this could be real helpful. _Originally posted by @chrysle in https://github.com/pypa/packaging.python.org/pull/1362#discussion_r1387128645_
Is it something that would be interesting for the guide in principle? Preview: * https://python-packaging-user-guide--1196.org.readthedocs.build/en/1196/discussions/packaging-tools-comparisons/ * https://github.com/sinoroc/packaging.python.org/blob/tools-comparison-tables/source/discussions/packaging-tools-comparisons.rst Plan is to add more tools, most notably conda and maybe also things...
The plugin should be able to read the credentials for alternative source repositories as they are configured via `poetry config ...` and somehow use them in tox. ***Related***: * #8...
The name for the plugin might not be fitting anymore. A more general name such as `tox-poetry-helpers` might be a better fit.
There should be a way to instruct Tox to install the pinned versions as read from Poetry's lock file. **_UX_**: Probably from a UX point of view it could look...
GitHub: https://github.com/sinoroc/tox-poetry-dev-dependencies/issues/24