The latest version of the `pantsbuild.pants` pypi,...
# plugins
f
The latest version of the
pantsbuild.pants
pypi, is
2.17.1
Is it possible to have this updated ?
Look like the 2.18.dev series were uploaded
Copy code
>2.17.1,<2.18.0.dev0 || >2.18.0.dev0,<2.18.0.dev1 || >2.18.0.dev1,<2.18.0.dev3 || >2.18.0.dev3,<2.18.0.dev4 || >2.18.0.dev4,<2.18.0.dev5 || >2.18.0.dev5,<2.18.0.dev6 || >2.18.0.dev6,<2.18.0.dev7 || >2.18.0.dev7,<2.18.0a0 || >2.18.0a0,<3.0.0
but no 2.18 published, or 2.19, 2.20
n
The release process changed in 2.18. 2.17 was the last release that was published to PyPI, now releases are published to GitHub instead.
f
It looks like the PyPI repository, on github, is not a conformant PyPI
simple
repository. poetry is trying to hit, a subdirectory which does not exist. (I can see that it is
gh-pages
over the top the the github releases - or similar. Looks like the index needs some extra folders added.
my work around was to add the URL to the arch/ os directly
b
To avoid an X-Y problem, what are you trying to do that requires depending on pants internals like this? (Also, are you aware of https://www.pantsbuild.org/2.19/reference/targets/pants_requirements ?)
f
oh - just the local "vscode" .venv imports to make the plugin development easier. •
pants_requirements(..)
- lol been using pants for over 2.5 years - never saw this one šŸ˜„ lol. Using that - i would then want to drop a "venv" in the local plugins folder - generated from that .. i;ll explore.
b
I think you should be able to
pants export
the resolve with that, to get a venv containing it
šŸ‘ 1
b
You're correct though that the index likely isn't a valid pypi simple index. It's meant to be used with --find-links support from pip