Re: [Python-Dev] Non-stable pyc results on python 3.6

On 28 Jul 2017 00:54, "Nick Coghlan" wrote: The fact that disorderfs makes a difference does make me a little suspicious, as there's an early exit from the FLAG_REF setting code related to objects having exactly one live reference. Courtesy of string interning and other

Re: [Python-Dev] Non-stable pyc results on python 3.6

On 27 July 2017 at 23:48, jan matejek wrote: > This is most often found in __init__.py. Often this affects optimized pycs, > but we can see it in > un-optimized as well. > The issue is rare -- 99% of all pycs are stable -- but when it occurs, it's > easy to replicate it in >

[Python-Dev] Non-stable pyc results on python 3.6

hello, we're seeing strange problems when trying to do reproducible builds of some python 3.6 modules. Namely, from one build to another, there will be something like the following difference in the compiled object: 4e40 da 07 5f 5f 61 6c 6c 5f 5f da 0a 5f 5f 61 75 74