Skip to content

Conversation

hoodmane
Copy link
Contributor

@hoodmane hoodmane commented Dec 3, 2024

Fixed one spot where there was invalid html (script tag closed twice). Other than that, this gives consistent usage of semicolons, quotes, indentation, etc. Separated out into its own commit for ease of review.

Fixed one spot where there was invalid html (script tag closed twice). Other
than that, this gives consistent usage of semicolons, quotes, indentation, etc.
Separated out into its own commit for ease of review.
Copy link
Contributor

@freakboy3742 freakboy3742 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewing format change PRs is always hard, but AFAICT this is all straightforward stuff. One question inline about some metadata that probably needs feedback from @katharosada, and we should be good to go.

<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Katie Bell" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to deny @katharosada credit here - but should this author be preserved? My concern is that given this is example code, the likelihood of the <head> block being copy-pastad into other projects seems high. Looking at other code in the Python codebase, the only places a specific name is called out is in a copyright assertion; and there, it's always in a comment, rather than in something that is "externally visible" as it would be here.

Unless there's a credit or copyright assertion reason for preserving this, I think we'd be better served removing the author meta tag - but I don't want to do that without @katharosada's informed consent.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree it might make sense to remove this author tag. But shouldn't this be done in a separate PR? I'd like to keep all the automatic noisy formatting changes by themselves?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough - I can live with that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty sure that author tag was added automatically by my IDE or some plugin when I created the HTML file, I didn't even notice it.
Feel free to remove, no argument here!

@bedevere-app
Copy link

bedevere-app bot commented Dec 4, 2024

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Katie Bell" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough - I can live with that.

@freakboy3742 freakboy3742 merged commit 2f1cee8 into python:main Dec 5, 2024
56 of 58 checks passed
srinivasreddy pushed a commit to srinivasreddy/cpython that referenced this pull request Jan 8, 2025
…ython#127551)

Cleaned up formatting (and a stray closing tag) of the web example HTML and JS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants