You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Binary objects built on a CPython that's built with Pydebug (--with-pydebug) are incompatible with objects built on non-pydebug CPythons (this is the d in PEP 425 tags). The software I work on for my day job has a pretty big list of slow-to-build C extension dependencies, and on the occasions that I need to use Pydebug while working a problem, it'd be handy to have prebuilt wheels around that are kept up to date by our wheel building automation.
Pydebug builds shouldn't be included in the standard image so as to keep the image size down, but we could build a separate image that included them.
This discussion was converted from issue #122 on October 29, 2022 08:02.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Binary objects built on a CPython that's built with Pydebug (
--with-pydebug) are incompatible with objects built on non-pydebug CPythons (this is thedin PEP 425 tags). The software I work on for my day job has a pretty big list of slow-to-build C extension dependencies, and on the occasions that I need to use Pydebug while working a problem, it'd be handy to have prebuilt wheels around that are kept up to date by our wheel building automation.Pydebug builds shouldn't be included in the standard image so as to keep the image size down, but we could build a separate image that included them.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions