| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I believe that the 6 lines from 1205 to 1210 can be replaced by 2 lines -- an re.match and an f-string. I will submit an alternate proposal later. I believe that the input vevent name should have either no <>s or 2 of each, with maybe the latter for back compatibility (I will test). But I will may stick with the more general code to not break buggy extensions. |
Sorry, something went wrong.
There was a problem hiding this comment.
Assuming this is the fix that we go with, let's add a test case.
Sorry, something went wrong.
|
@terryjreedy so should I leave the code for now, or should I go ahead
and replace with the re.match thing you are going to propose?
@ZeroIntensity so do you mean that active voice is preferred in
release notes? I can replace this specific case with the change that
you are suggesting, but I'm asking for advice in this aspect for
future News.
|
Sorry, something went wrong.
|
Yes, I think it can be. Will fix.
… Message ID: ***@***.***>
|
Sorry, something went wrong.
|
@johnzhou721 Lines 1373 to 1378 in 5ab66a8 As an example, I successfully utilized Gemini 2.5 Pro to generate a reasonable fix for this problem. Could you give it a try? |
Sorry, something went wrong.
|
@kexinoh Yes, I would give it a try once I have time; however, I am working on something else right now -- is it acceptable if I delay this by about a day or so? (if anyone else has a fix ready before I get to this, feel free to make a pr onto the branch of my pr and I'll merge it into my PR) |
Sorry, something went wrong.
…dziqkQ.rst Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
|
@kexinoh I have a small amount of time not enough to work on anything else before I end my day so I attempted the issue you pointed out -- but can't test though. |
Sorry, something went wrong.
Where? How? For what? Thanks! @ZeroIntensity |
Sorry, something went wrong.
We need a test case in test_idlelib that results in DOS/extreme slowness off main. Basically, just do something to prove that this PR fixes it (probably just testing with large amounts of data). |
Sorry, something went wrong.
|
Can the PR title be changed to be more useful? Every PR is a change. Good titles say «Add thing to spam» or «Fix eggs with ham» |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 90 days with no activity. |
Sorry, something went wrong.
|
Thanks @johnzhou721 for the PR, and @zware for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
Sorry, something went wrong.
|
GH-156911 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
GH-156912 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
|
GH-156913 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
…methodname processing (pythonGH-134874)
| Back | FazBrowse Home | New Git URL |
A DOS by Quadratic complexity issue is fixed in idlelib. Part of (but does not fix) #134873.