On 11 April 2018 at 02:54, Antoine Pitrou wrote:
> On Tue, 10 Apr 2018 19:29:18 +0300
> Serhiy Storchaka
> wrote:
>>
>> A bugfix release can fix bugs in bytecode generation. See for example
>> issue27286. [1] The part of issue33041 backported to 3.7 and 3.6 is an
>> other example. [2] There wer
On Tue, 10 Apr 2018 19:29:18 +0300
Serhiy Storchaka
wrote:
>
> A bugfix release can fix bugs in bytecode generation. See for example
> issue27286. [1] The part of issue33041 backported to 3.7 and 3.6 is an
> other example. [2] There were other examples of compatible changing the
> bytecode.
10.04.18 18:58, Antoine Pitrou пише:
On Tue, 10 Apr 2018 18:49:36 +0300
Serhiy Storchaka
wrote:
3. The number of compatible subversion. Currently the interpreter
supports only a single magic number. If the updated version of the
compiler produces more optimal or more correct but compatible byte
On Tue, 10 Apr 2018 18:49:36 +0300
Serhiy Storchaka
wrote:
>
> 1. More stable file signature. Currently the magic number is changed in
> every feature release. Only the third and the forth bytes are stable
> (b'\r\n'), the first bytes are changed non-predicable. The 'py' launcher
> and third-p
The format of the header of pyc files was stable for long time and
changed only few times. First time it was changed in 3.3: added the size
of the corresponding source mod 2**32. [1] Second time it was changed
in 3.7: added the 32-bit flags field and support of hash-based pyc files
(PEP 552).