-
-
Notifications
You must be signed in to change notification settings - Fork 348
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2193 from tjstum/noleak
- Loading branch information
Showing
7 changed files
with
125 additions
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
Trio now deterministically cleans up file descriptors that were opened before | ||
subprocess creation fails. Previously, they would remain open until the next run of | ||
the garbage collector. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
This directory collects "newsfragments": short files that each contain | ||
a snippet of ReST-formatted text that will be added to the next | ||
release notes. This should be a description of aspects of the change | ||
(if any) that are relevant to users. (This contrasts with your commit | ||
message and PR description, which are a description of the change as | ||
relevant to people working on the code itself.) | ||
|
||
Each file should be named like ``<ISSUE>.<TYPE>.rst``, where | ||
``<ISSUE>`` is an issue number, and ``<TYPE>`` is one of: | ||
|
||
* ``headline``: a major new feature we want to highlight for users | ||
* ``breaking``: any breaking changes that happen without a proper | ||
deprecation period (note: deprecations, and removal of previously | ||
deprecated features after an appropriate time, go in the | ||
``deprecated`` category instead) | ||
* ``feature``: any new feature that doesn't qualify for ``headline`` | ||
* ``bugfix`` | ||
* ``doc`` | ||
* ``deprecated`` | ||
* ``misc`` | ||
|
||
So for example: ``123.headline.rst``, ``456.bugfix.rst``, | ||
``789.deprecated.rst`` | ||
|
||
If your PR fixes an issue, use that number here. If there is no issue, | ||
then after you submit the PR and get the PR number you can add a | ||
newsfragment using that instead. | ||
|
||
Your text can use all the same markup that we use in our Sphinx docs. | ||
For example, you can use double-backticks to mark code snippets, or | ||
single-backticks to link to a function/class/module. | ||
|
||
To check how your formatting looks, the easiest way is to make the PR, | ||
and then after the CI checks run, click on the "Read the Docs build" | ||
details link, and navigate to the release history page. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters