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

DOC: Wrong bug number in what's new v3.0.0 #59532

Closed
1 task done
matsidzi opened this issue Aug 16, 2024 · 3 comments · Fixed by #59539
Closed
1 task done

DOC: Wrong bug number in what's new v3.0.0 #59532

matsidzi opened this issue Aug 16, 2024 · 3 comments · Fixed by #59539

Comments

@matsidzi
Copy link
Contributor

Pandas version checks

  • I have checked that the issue still exists on the latest versions of the docs on main here

Location of the documentation

https://pandas.pydata.org/docs/dev/whatsnew/v3.0.0.html

Documentation problem

There is a sentence in the Bug Fixes > Datetimelike section:

"Bug in date_range() where using a negative frequency value would not include all points between the start and end values (GH 56382)"

The "56382" is a wrong number which is not related to the fixed issue.

The correct PR is #56832.
The correct issue is #56147.

Suggested fix for documentation

Fix "56382" to "56147" in the mentioned line in what's new v3.0.0.

@matsidzi matsidzi added Docs Needs Triage Issue that has not been reviewed by a pandas team member labels Aug 16, 2024
@matsidzi
Copy link
Contributor Author

I'm not sure if this is a problem or not, but I decided to add it here as a comment. Maybe these bugs:
#56147
#56134
need to be closed, because related PRs are merged.

@rhshadrach rhshadrach removed the Needs Triage Issue that has not been reviewed by a pandas team member label Aug 16, 2024
@Aloqeely
Copy link
Member

Thanks for the report. PRs are welcome!

@matsidzi
Copy link
Contributor Author

take

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

Successfully merging a pull request may close this issue.

3 participants