Pre-release version of a package not found even with `--allow-prereleases`
See original GitHub issue- I am on the latest Poetry version.
- I have searched the issues of this repo and believe that this is not a duplicate.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).
- OS version and name: archlinux
- Poetry version: 1.1.4
- Python version: 3.7.7
Issue
I am trying to install a pre-release verion of https://github.com/elastic/enterprise-search-python
Their recommended installation method is
python -m pip install --pre elastic-enterprise-search which works fine.
When trying to install it with poetry using
poetry add --allow-prereleases elastic-enterprise-search I am getting an old version: 0.2.1 (the same as the one without the
--allow-prereleases
switch.
Am I doing something wrong? Or is it that this package is configured incorrectly?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:23 (13 by maintainers)
Top Results From Across the Web
Install-Module : A parameter cannot be found that matches ...
Recently I started to utilize Prerelease option for my PowerShell Modules. This allows me to early test them before I release them to...
Read more >Install-Module : A parameter cannot be found that matches ...
A parameter cannot be found that matches parameter name. To try a prerelease of PowerShell modules, you need to specify the AllowPrerelease parameter,...
Read more >AzureArtifactsPowerShellModule...
Write-Information "The NuGet package provider is not installed." ... AllowPrerelease: If provided, prerelease versions are allowed to be installed and ...
Read more >Install-Module ExchangeOnlineManagement - r/PowerShell
Specifically I need the prerelease version 2.0.6-PreviewX. The problem I started with is that I didn't have the -AllowPrerelease option.
Read more >Prerelease Module Versions - PowerShell
Identifying a module version as a prerelease; Finding and acquiring ... If -AllowPrerelease flag is not specified, prerelease packages will ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
looks like doing:
works fine for poetry 1.1.5 works just fine for me. If allowing pre-releases just adding a wildcard
*
is probably the best bet to get the latest pre-release.I have the same problem with poetry 1.1.5. All private repos so I can’t point out to the given packages, but essentially:
does not resolve to using the
3.0.0.dev0
version, while if I write directly:poetry works fine.
But maybe there is a standard way of defining prerelease versions I am missing?