-
-
Notifications
You must be signed in to change notification settings - Fork 946
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
chore(3.1.2): prepare first beta release of 3.1.2 #2188
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
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 |
---|---|---|
@@ -1 +1,7 @@ | ||
:class:`~falcon.testing.TestCase` mimics behavior of real WSGI servers following WSGI spec where is said that ``PATH_INFO`` CGI variable for WSGI app is already percent-decoded. However, this breaks routing if slash (encoded as ``%2F``) is part of path element, not a path separator, as explained in the FAQ :ref:`routing_encoded_slashes`. The workaround based on some WSGI servers' non-standard CGI variables described in :ref:`raw_url_path_recipe` recipe breaks tests because :py:func:`falcon.testing.helpers.create_environ` hard-code CGI variable ``RAW_URI`` to ``/`` instead to real path *before* percent-decoding. | ||
Falcon's :class:`~falcon.testing.TestClient` mimics the behavior of real WSGI | ||
servers (and the WSGI spec) by presenting the ``PATH_INFO`` CGI variable | ||
already in the percent-decoded form. However, the client also used to | ||
indiscriminately set the non-standard ``RAW_URI`` CGI variable to ``/``, which | ||
made writing tests for apps :ref:`decoding raw URL path <raw_url_path_recipe>` | ||
cumbersome. This has been fixed, and the raw path of a simulated request is now | ||
preserved in ``RAW_URI``. |
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 @@ | ||
Changelog for Falcon 3.1.1 | ||
========================== | ||
|
||
Summary | ||
------- | ||
|
||
This is a minor point release fixing a couple of high impact bugs, | ||
as well as publishing binary wheels for the recently released CPython 3.12. | ||
|
||
|
||
Changes to Supported Platforms | ||
------------------------------ | ||
|
||
- Falcon is now supported (including binary wheels) on CPython 3.12. | ||
A couple of remaining stdlib deprecations from 3.11 and 3.12 will be | ||
addressed in Falcon 4.0. | ||
- As with the previous release, Python 3.5 & 3.6 remain deprecated and | ||
will no longer be supported in Falcon 4.0. | ||
- EOL Python 3.7 will no longer be actively supported in 4.0, but the framework | ||
should still continue to install from source. We may remove the support for | ||
3.7 altogether later in the 4.x series if we are faced with incompatible | ||
ecosystem changes in typing, Cython, etc. | ||
|
||
|
||
.. towncrier release notes start | ||
|
||
Contributors to this Release | ||
---------------------------- | ||
|
||
Many thanks to those who contributed to this bugfix release: | ||
|
||
- `CaselIT <https://github.com/CaselIT>`__ | ||
- `kgriffs <https://github.com/kgriffs>`__ | ||
- `liborjelinek <https://github.com/liborjelinek>`__ | ||
- `vytas7 <https://github.com/vytas7>`__ |
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 |
---|---|---|
|
@@ -3,6 +3,7 @@ Changelogs | |
|
||
.. toctree:: | ||
|
||
3.1.2 <3.1.2> | ||
3.1.1 <3.1.1> | ||
3.1.0 <3.1.0> | ||
3.0.1 <3.0.1> | ||
|
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
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for me it's fine to also remove 3.7 support for v4, but I don't think it's high impact since there aren't much improvements.
3.8 would be higher impact since targeting 3.9+ allows the
type | type
typing syntax to work. But it's not yet that time :)