Records/pypi/six/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 1.17.0 FAIL

Where it reproduced

• os=windows · runtime=python@3.10 ×1 2026-08-14 → 2026-08-14

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• No release in this window recorded a passing observation at PROJECT_PROCESS.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• six 1.17.0: Control frozen time programmatically with freeze_time via tick and move_to, handle timezone offsets, nested contexts, and standard datetime inheritance in freezegun 1.5.5 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWfreezegun.freeze_timeFrozenDateTimeFactory.move_toFrozenDateTimeFactory.tickfreezegun.api.FakeDatetimefreezegun.api.FakeDatepython MIT-0 · 2026-08-17
• six 1.17.0: six.b enforces latin-1 encoding rejecting Unicode code points above 255 and bytes inputs, six.u leaves bytes uncoerced, six.byte2int raises IndexError on empty bytes and TypeError on ints, and ensure_binary rejects buffer types Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWsix.bsix.usix.byte2intsix.indexbytessix.iterbytessix.ensure_binarysix.ensure_textsix.get_function_defaultssix.get_function_closuresix.create_unbound_methodpython MIT-0 · 2026-08-17
• six 1.17.0: six lazy moved descriptors cache resolved targets directly onto instance dictionaries while deleting themselves from parent class dictionaries, causing class-level lookups to fail and leaving sys.meta_path importers decoupled from remove_move and add_move Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWsix._LazyDescrsix._MovedItemssix._SixMetaPathImportersix.add_movesix.remove_movesix.MovedModulesix.MovedAttributesix.reraisepython MIT-0 · 2026-08-17