New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pythonPackages.cachy: 0.2.0 -> 0.3.0 #72445
Conversation
@GrahamcOfBorg build poetry python27Packages.cachy python27Packages.poetry python37Packages.cachy python38Packages.cachy python38Packages.poetry |
repo = "poetry"; | ||
rev = version; | ||
sha256 = "004s747wkil5f00r0vjff73r6vhlrrcnfan2k7pl7gyf62wfp02a"; | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If needs must, I guess - at least both package fetches are based on the same version
so they shouldn't diverge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, which is why i moved the version to the the let scope...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only way I thought i could sneak tests in... didn't want to break it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plus, there's apparently no packages that use poetry to build... so i can't use them as a way to verify correctness :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the source can be used by using format = "pyproject";
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the raw source of poetry can't be installed without a previous version of poetry, the github pull is just to get the tests.
|
@GrahamcOfBorg build poetry python27Packages.cachy python27Packages.poetry python37Packages.cachy python38Packages.cachy python38Packages.poetry not sure why darwin's tests are still all passing, but then the drv still fails to build.... |
oh python38Packages.rednose is broken, the other's are good @FRidh is this too hacky for you? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually wait I think it can be done...
@jonringer how hacky is this? :-D |
I'll try again by modifying the python path, might be possible |
I feel like that would make it a pain to update :) |
I don't know. As long as poetry works directly from the source directory, I don't see any problem with it. Replacing versions is essentially the same as using |
Regarding poetry again. In the future pip will support self-hosting backends, so the |
Motivation for this change
closes #67043
Added tests to make sure I wasn't breaking anything when removing version bound. Unfortunately, poetry is self-bootstrapping (i.e. need a previous version to install it), I had to do both a pypi fetch for the installation, and a github fetch for the tests.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @