OTOH, we're talking about a doc fix for a very old version. Surely
people who rely on the documented opcodes there have already fixed their
software to deal with the discrepancy.
Regards
Antoine.
Le 08/07/2018 à 18:44, Serhiy Storchaka a écrit :
> 08.07.18 13:02, Larry Hastings пише:
>> On 07
08.07.18 13:02, Larry Hastings пише:
On 07/08/2018 01:31 AM, Serhiy Storchaka wrote:
I suggest to merge a 3.5 specific documentation fix for
CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW opcodes. There were
undocumented changes in 3.5, and third-party projects which implement
interpreting or gene
On 07/08/2018 01:31 AM, Serhiy Storchaka wrote:
I suggest to merge a 3.5 specific documentation fix for
CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW opcodes. There were
undocumented changes in 3.5, and third-party projects which implement
interpreting or generating these opcodes do it incorrectly
08.07.18 10:45, Larry Hastings пише:
My six-month cadence means it's time for the next releases of 3.4 and
3.5. There haven't been many changes since the last releases--two, to
be exact. These two security fixes were backported to both 3.4 and 3.5:
* bpo-32981: Fix catastrophic backtrackin
My six-month cadence means it's time for the next releases of 3.4 and
3.5. There haven't been many changes since the last releases--two, to
be exact. These two security fixes were backported to both 3.4 and 3.5:
* bpo-32981: Fix catastrophic backtracking vulns (GH-5955)
* bpo-33001: Prev
