Skip to content
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

cherry-pick PR #3406 for v1.1 #4241

Merged
merged 2 commits into from Jul 3, 2021
Merged

cherry-pick PR #3406 for v1.1 #4241

merged 2 commits into from Jul 3, 2021

Conversation

jstriebel
Copy link
Contributor

This cherry-picks #3406 for v1.1 for a new patch-release. From the original PR:

Add PyPI registry correctly to pool depending on other sources (#3406)

In the event where we defined sources that were set as
secondary = True, we would end up with PyPI being after this source
when it should have acted as default in that case.

The main issue stems from the fact that it's not because you have
sources configured that PyPI should not be a default. Instead, PyPI
should be default if there are no sources with secondary = False and
not default if there are sources with secondary = True.

Pull Request Check List

Related to PR #3406, resolves #2339, resolves #3306, resolves #3238 for v1.1

Add PyPI registry correctly to pool depending on other sources (#3406)

In the event where we defined sources that were set as
secondary = True, we would end up with PyPI being after this source
when it should have acted as default in that case.

The main issue stems from the fact that it's not because you have
sources configured that PyPI should not be a default. Instead, PyPI
should be default if there are no sources with secondary = False and
not default if there are sources with secondary = True.
@jstriebel
Copy link
Contributor Author

It's not clear to me why the CI fails with

ValueError

Incorrectly nested style tag found.

Seems like the random error from #3010. The tests seem to work fine locally.

@jstriebel
Copy link
Contributor Author

@sdispater Since you merged the original PR, could you have a look at this cherry-pick for v1.1? Thanks a lot!

@sonarcloud
Copy link

sonarcloud bot commented Jul 1, 2021

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@abn
Copy link
Member

abn commented Jul 3, 2021

@jstriebel approving and merging this one. However, please note that we do not at present have a plan for another 1.1 release.

@abn abn merged commit 7504b33 into python-poetry:1.1 Jul 3, 2021
@jstriebel jstriebel deleted the 1.1 branch July 4, 2021 12:24
@jstriebel jstriebel restored the 1.1 branch July 4, 2021 12:25
@caniko
Copy link

caniko commented Jul 4, 2021

@jstriebel approving and merging this one. However, please note that we do not at present have a plan for another 1.1 release.

But it is a broken feature, shouldn't broken features be patched? Especially for those who won't upgrade to the next major/minor?

PS: Not pushing a patch for this bug is a minor mistake

@jstriebel jstriebel deleted the 1.1 branch July 6, 2021 08:11
@jstriebel
Copy link
Contributor Author

jstriebel commented Jul 6, 2021

@abn Thanks for merging!

However, please note that we do not at present have a plan for another 1.1 release.

Understandable, however it would be very useful, especially considering that 1.2 introduces bugs that might keep someone from upgrading to that version (in my case #4254). I'm therefore using the commit of this PR to install poetry atm.

@sdispater sdispater mentioned this pull request Aug 19, 2021
@sdispater sdispater mentioned this pull request Sep 18, 2021
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants