Patch to Python uuid module to avoid CRT warning on Windows #38364
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#38364
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There is a bug in Python's
uuid
module that has been affecting official Blender releases on Windows for several years. It's triggered by Blender's inclusion of the CRT redistributables, and causes a runtime exception to be thrown when the module is first imported. It's harmless, but the OS "runtime error" window that appears is disconcerting for users and a thorn in the side of anyone whose addon usesuuid
.In uuid.py I've applied the fix suggested in Python's bug tracker, and it works just fine. It would be good to get it into the next Blender release.
The file is located at
lib/*/release/python33.tar.gz/uuid.py
. I don't know how Git would handle changes to that file...perhaps a "patches" subdir and change to the INSTALL project would be appropriate?Changed status to: 'Open'
Added subscriber: @artfunkel
Added subscriber: @mont29
Thomas, as Windows release manager, I think this one is for you :)
Any chance to fix this upstream rather than hacking it on our side?
I also rather let vc2008 libs die and don't change them again. We will switch to vc2012 or 2013 after the 2.70 release.
Since I added Python 3.3 to the list of affected platforms the bug has been getting a bit of attention, but seeing as it was reported two years ago let's not hold our breath...
Added subscriber: @ideasman42
Some nasty workarounds...
Infact simply temp overwriting CDLL works
Added subscriber: @Wiz
Changed status from 'Open' to: 'Resolved'
With Python3.4x and MSVC2013, this is now resolved. closing.