Date: Fri, 16 Jun 2023 23:55:05 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 269777] sysutils/py-ansible-core: checksum errors Message-ID: <bug-269777-227-tfkdhnEFFd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-269777-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269777 --- Comment #6 from Charlie Li <vishwin@freebsd.org> --- Checksums for Python bytecode are dubious at best considering their non-deterministic characteristics. There is absolutely no guarantee that bytecode compiled during one run will match another bytecode compile run, on the same original Python source, at the byte-for-byte level (which is what our checksums operate on), even though they are more likely than not functionally equivalent. This is a known problem in CPython land that not only does not have any easy answers, but also not a priority to tackle. This is principally why bytecode should be compiled *after* install (not during package) and only if the user wants them. imo CPython bytecode architecture is one of the most boneheaded decisions I've ever seen, particularly when interacting with distro (in their parlance) package systems, that *need* to operate on a byte-for-byte level. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269777-227-tfkdhnEFFd>