Skip to content

Clarify why two or one spaces and code formatting #1010

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Oct 8, 2020
Merged

Clarify why two or one spaces and code formatting #1010

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
22ebe3b
Clarify why two or one spaces and code formatting
humitos Oct 8, 2020
5ff2ded
Backticks and *
humitos Oct 8, 2020
646c51f
Update .overrides/faq.rst
humitos Oct 8, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Backticks and *
  • Loading branch information
@humitos
humitos committed Oct 8, 2020
commit 5ff2ded9ba638e084d8a8637fc45a970c275bb18
3 changes: 2 additions & 1 deletion .overrides/faq.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,7 +233,8 @@ Si aparece el nombre de una función (por ejemplo, "IncrementalParser") en el or
(no está en cursiva, ni en negrita ni en estilo de código), aunque sientas la tentación de ponerla como
``IncrementalParser``, no debes hacerlo.

En principio, no debemos cambiar el formato de estas palabras. Si realmente crees que es un error y debería
En principio, no debemos cambiar el formato de estas palabras. Si está con asteriscos, lo dejamos con asteriscos.
Si está con backticks, lo dejamos con los backticks, etc. Si realmente crees que es un error y debería
estar con un formato distinto, debes reportarlo en el repositorio de CPython.


Expand Down