diff options
| author | ptmcg <ptmcg@austin.rr.com> | 2022-11-06 17:31:29 -0600 |
|---|---|---|
| committer | ptmcg <ptmcg@austin.rr.com> | 2022-11-06 17:31:29 -0600 |
| commit | e9b0b1ba2a0c3e21dc46e16ae5274ae7aa3cb044 (patch) | |
| tree | 4e1cc1c3bb05b3b5490fce0c6b54264e501ff760 | |
| parent | c1d239103c0060212e59f99171ccc4d8405420eb (diff) | |
| download | pyparsing-git-e9b0b1ba2a0c3e21dc46e16ae5274ae7aa3cb044.tar.gz | |
Update proposed release timings for 3.1.0 and 4.0
| -rw-r--r-- | CHANGES | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -6,9 +6,9 @@ Version 3.0.10 - (in development) --------------------------------- NOTE: In the future release 3.1.0, use of many of the pre-PEP8 methods (such as `ParserElement.parseString`) will start to raise `DeprecationWarnings`. 3.1.0 should -get released some time in August or September, 2022. I currently plan to completely +get released some time in early 2023. I currently plan to completely drop the pre-PEP8 methods in pyparsing 4.0, though we won't see that release until -at least late 2023. So there is plenty of time to convert existing parsers to +at least late 2023 or early 2024. So there is plenty of time to convert existing parsers to the new function names before the old functions are completely removed. (Big help from Devin J. Pohly in structuring the code to enable this peaceful transition.) |