|
2 | 2 | Release Notes |
3 | 3 | ============= |
4 | 4 |
|
5 | | -.. _Release Notes_1.0.6-12: |
| 5 | +.. _Release Notes_1.0.7: |
| 6 | + |
| 7 | +1.0.7 |
| 8 | +===== |
| 9 | + |
| 10 | +.. _Release Notes_1.0.7_Upgrade Notes: |
| 11 | + |
| 12 | +Upgrade Notes |
| 13 | +------------- |
| 14 | + |
| 15 | +- With werkzeug 2.3.x the headers type has been updated to not allow integers as header values. This restriction followed up in pytest-httpserver. |
6 | 16 |
|
7 | | -1.0.6-12 |
8 | | -======== |
9 | 17 |
|
10 | | -.. _Release Notes_1.0.6-12_Bug Fixes: |
| 18 | +.. _Release Notes_1.0.7_Deprecation Notes: |
| 19 | + |
| 20 | +Deprecation Notes |
| 21 | +----------------- |
| 22 | + |
| 23 | +- Python versions earlier than 3.8 have been deprecated in order to support |
| 24 | + the latest werkzeug. Users using 3.7 or earlier python may use |
| 25 | + pytest-httpserver with earlier werkzeug versions but tests are no longer run |
| 26 | + for these python versions. |
| 27 | + |
| 28 | + |
| 29 | +.. _Release Notes_1.0.7_Bug Fixes: |
11 | 30 |
|
12 | 31 | Bug Fixes |
13 | 32 | --------- |
14 | 33 |
|
15 | 34 | - Type hinting for header_value_matcher has been fixed. From now, specifying a |
16 | | - callable as `Callable[[str, Optional[str], str], bool]` will be accepted |
17 | | - also. Providing a `HeaderValueMatcher` object will be also accepted as |
| 35 | + callable as ``Callable[[str, Optional[str], str], bool]`` will be accepted |
| 36 | + also. Providing a ``HeaderValueMatcher`` object will be also accepted as |
18 | 37 | before, as it provides the same callable signature. |
19 | 38 |
|
| 39 | +- Fix Werkzeug deprecation warning about ``parse_authorization_header`` call. |
| 40 | + Replace ``parse_authorization_header`` with ``Authorization.from_header`` as |
| 41 | + suggested. This fix should not introduce any functional change for the |
| 42 | + users. |
| 43 | + |
| 44 | +- Fix Werkzeug deprecation warning about ``werkzeug.urls.url_decode`` call. This |
| 45 | + call has been changed to ``urllib.parse.parse_qsl`` in the implementation. |
| 46 | + This fix should not introduce any functional change for the users. |
| 47 | + |
20 | 48 |
|
21 | 49 | .. _Release Notes_1.0.6: |
22 | 50 |
|
|
0 commit comments