funny ;
this made me think of this talk;
https://youtu.be/OSGv2VnC0go?t=1013
Éric Lafontaine | Membre du Projet VUE, Groupe Contrôle
Génie électrique, 54ème promotion UdeS | Étudiant en maitrise TI à l'ETS
VAS OPS chez Bell Mobility
« Nous voulons proposer une alternative de transport en
On 2017-07-27 03:34, Mike Miller wrote:
On 2017-07-26 16:36, MRAB wrote:
"nobreak" would introduce a new keyword, but "not break" wouldn't.
Whenever I've used the for-else, I've put a # no-break right next to it, to
remind myself as much as anyone else.
for...: not break: is the best
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
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
>
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