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

"Latest news" should link to articles on blog.python.org not pythoninsider.blogspot.com #2685

Open
hugovk opened this issue Jan 14, 2025 · 3 comments
Labels
bug This is a bug!

Comments

@hugovk
Copy link
Member

hugovk commented Jan 14, 2025

Describe the bug

"Latest news" at https://www.python.org/ links articles to pythoninsider.blogspot.com but the "More" link goes to blog.python.org.

Both should go to blog.python.org.

To Reproduce

  1. Go to https://www.python.org/ and find "Latest news"
Image
  1. The first article link is to https://pythoninsider.blogspot.com/2025/01/python-3140-alpha-4-is-out.html
  2. (The others are to articles on https://pyfound.blogspot.com/, not relevant here)
  3. The "More" link goes to https://blog.python.org/

Expected behavior

https://blog.python.org/ and https://pythoninsider.blogspot.com are the same thing, but with two domains.

The first article link should go to the nicer blog.python.org URL, not the blogspot one.

Possibly related to or fixed by #2662, but perhaps the URLs need rewriting?

URL to the issue

https://www.python.org

Browsers

Chrome

Operating System

macOS

Browser Version

132

@hugovk hugovk added the bug This is a bug! label Jan 14, 2025
@hugovk hugovk changed the title Bug: <title> "Latest news" should link to articles on blog.python.org not pythoninsider.blogspot.com Jan 14, 2025
@ONKARBH
Copy link

ONKARBH commented Jan 19, 2025

Hi @hugovk, I'd like to work on this issue. Could you please assign it to me?

@hugovk
Copy link
Member Author

hugovk commented Jan 19, 2025

Hi @ONKARBH! I don't think we usually assign issues to people, because often they disappear without notice, and it deters other people to work on it if they see an already-assigned issue.

I'm not sure if this will be fixed by config changes needed for #2662, but you can have a look if there's something that could be fixed in this codebase?

@ONKARBH
Copy link

ONKARBH commented Jan 20, 2025

@hugovk "Got it! I'll start working on the issue and will address any changes I find. Your point is valid, and I’ll ensure others have the chance to work on the issue as well while I'm working on it. Thanks!"

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

No branches or pull requests

2 participants