Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience.
...Markdown support and message preview and editing. This feature will allow the use of Markdown in messages and the ability to preview the message before the submission and edit it afterward. This can be done, but it will take some work. Possible solutions have been proposed on the roundup-devel mailing list [7]. "Remove me from nosy list" button. Add a button on issue pages to remove self from the nosy list. This feature will be added during GSoC 2019. Mobile friendly theme. Current theme o...
...markdown and emoji. Preview tab, showing how a comment will be rendered, prior to actually posting. Support for voting via reactions. Support for permalinks [5], allowing easy quoting and copying & pasting of source code. It is possible to automatically embed code snippet on GitHub by pasting a permalink. Core developers, volunteers, and the PSF don't have to maintain the issue infrastructure/site, giving us more time and resources to focus on the development of Python. Ability to automatica...
...Markdown or ReStructured Text to describe your release. The former is less verbose, while the latter has nifty integration for things like referencing PEPs. Leave the "Release page" field on the form empty. "Save" the release. Populate the release with the downloadable files. Your friend and mine, Georg Brandl, made a lovely tool called "add-to-pydotorg.py". You can find it in the "release" tree (next to "release.py"). You run the tool on downloads.nyc1.psf.io, like this: $ AUTH_INFO=<u...
...Markdown: .md AsciiDoc: .adoc, .asc, .asciidoc HTML: .html, .htm Automated tools MAY render one or more of the specified formats as plain text and MAY render other markup formats beyond those listed. Automated tools SHOULD NOT make any assumptions regarding the maximum length of supporting document content, except as necessary to protect the integrity of a service. Example: "document_names": { "description": "README.rst", "license": "LICENSE.rst", "changelog": "NEWS" } The pyth...
...markdown. If the file path ends in a case-insensitive .rst, then tools MUST assume the content-type is text/x-rst. If a tool recognizes more extensions than this PEP, they MAY infer the content-type for the user without specifying this field as dynamic. For all unrecognized suffixes when a content-type is not provided, tools MUST raise an error. The readme field may also take a table. The file key has a string value representing a relative path to a file containing the full description. The text...