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

gh-126782: Support qualified referencing for ntpath.abspath() #119849

Closed
wants to merge 12 commits into from

Conversation

nineteendo
Copy link
Contributor

@nineteendo nineteendo commented May 31, 2024

@nineteendo nineteendo changed the title gh-119826: Improve accuracy of `ntpath.normpath() & ntpath.abspath() gh-119826: Improve accuracy of ntpath.normpath() & ntpath.abspath() May 31, 2024
@nineteendo nineteendo marked this pull request as ready for review May 31, 2024 13:34
@nineteendo nineteendo changed the title gh-119826: Improve accuracy of ntpath.normpath() & ntpath.abspath() gh-119826: Support qualified referencing for ntpath.abspath() Jun 2, 2024
@nineteendo

This comment was marked as outdated.

@nineteendo

This comment was marked as outdated.

@nineteendo
Copy link
Contributor Author

I never rebase, when I force push it's to redo a merge commit which failed here.

@nineteendo nineteendo marked this pull request as draft November 13, 2024 12:37
@nineteendo nineteendo changed the title gh-119826: Support qualified referencing for ntpath.abspath() gh-126782: Support qualified referencing for ntpath.abspath() Nov 13, 2024
…024-05-31-12-44-38.gh-issue-126782.Atm9ol.rst
@nineteendo
Copy link
Contributor Author

I'll fix the drive relative paths in a separate PR.

@ZeroIntensity
Copy link
Member

Two notes:

  • Please don't change the target issue after the PR has been opened, it makes it harder to track discussion.
  • I'd really prefer that this PR get closed and reopened as a fresh PR under the new issue. Incorrectly rebasing triggers a review from all the codeowners, and they don't get unsubscribed even after their review request is removed.

@nineteendo nineteendo closed this Nov 13, 2024
@nineteendo
Copy link
Contributor Author

Sorry for the chaos.

@nineteendo
Copy link
Contributor Author

It wasn't a rebase, I made a merge commit locally, but I realised I forgot to add the generated code. So I reset my head and committed without restarting the merge, causing the reviews to be requested. I force pushed afterwards to revert this commit in the hope it would remove the reviews (it didn't) with the intention of trying again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants