question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Packages with semvar+devnum schemas don't resolve.

See original GitHub issue
  • [ x] I am on the latest Poetry version.
  • [ x] I have searched the issues of this repo and believe that this is not a duplicate.
  • [ x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

Issue

A schema of seemingly increasingly popularity, especially in high-velocity projects, is the following:

(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(-(?P<stage>[^.]*)\.(?P<devnum>\d+))

For example: 0.2.1-alpha.26

It appears that poetry will not install packages that have such a version specification in their history. For example:

poetry add eth-keys

results in:

                                                         
[ValueError]                              
Could not find a matching version of package eth-keys  
                                                         
add [-D|--dev] [--git GIT] [--path PATH] [-E|--extras EXTRAS] [--optional] [--python PYTHON] [--platform PLATFORM] [--allow-prereleases] [--dry-run] [--] <name> (<name>)...

…despite eth-keys obviously being a valid package.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
fchorneycommented, Jan 3, 2019

What about the situation where a packages dependency only has prereleases? My solution was to just add that sub package manually, but I don’t think that should be the solution.

0reactions
stale[bot]commented, Nov 20, 2019

Closing this issue automatically because it has not had any activity since it has been marked as stale. If you think it is still relevant and should be addressed, feel free to open a new one.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Packages -> Table access rights between schemas
Packages do not "contain tables". Schema owns table & packages. Packages owned by USER_A inherit all privileges that have been GRANTED to USER_A....
Read more >
Package schema qualification using CURRENT ... - IBM
Package schemas provide a method for logically grouping packages. Different approaches exist for grouping packages into schemas.
Read more >
Is package.resolved generation not backwards compatible?
I don't believe a Package.resolved will switch to the version 2 schema until the package's Package.swift is updated to swift-tools-version:5.6 ...
Read more >
Controlling module resolution of zapatos/schema #49 - GitHub
I'm having difficulties getting my project to build. Essentially I want to create a publishable node module (let's call it my-db) that ...
Read more >
All of my .json files have problems loading reference/schema ...
I'm behind my company's proxy which I don't know the details because it's everything automatic, and this problem have bug me for some...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found