[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Marc Culler added the comment: Hi Ned, I have a comment about the code signing issues that would arise if the Tcl and Tk frameworks were embedded as actual subframeworks inside the Python.framework, and a user later replaced those with newer versions. The answer is that no new issues arise.

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Marc Culler added the comment: Ned - do you have any news on the topic of packaging Tcl/Tk within the Python bundle? -- ___ Python tracker ___

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Change by Aivar Annamaa : -- nosy: +Aivar.Annamaa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Ned Deily added the comment: Marc, thanks for your suggestion. I'm the one responsible for how Tcl and Tk are currently packaged in the python.org framework build and I know exactly what you are suggesting so there is no need for you to make a PR. There were reasons why I chose to set things

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Change by Ned Deily : -- assignee: -> ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Marc Culler added the comment: Dear Ronald, You are correct that "It is already possible to replace the Tcl/Tk libraries by replacing the relevant files in Python.framework." I know that because I have done it. Moreover, having done it, I know that it is much more difficult than it should be

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Ronald Oussoren added the comment: I'm not sure what you are trying to accomplish. It is already possible to replace the Tcl/Tk libraries by replacing the relevant files in Python.framework. However: these aren't meant to be user serviceable parts, the copy of Tcl/Tk that we include is test

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Marc Culler added the comment: Dear Eric, I am aware that python is cross platform. The change that I am proposing would be almost entirely limited to the file: Mac/BuildScript/build-installer.py which is entirely mac-specific. It controls how the Mac installer is constructed. Specifically

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

Eric V. Smith added the comment: It sounds like your solution is macOS only, where as Python needs to be cross platform. Further, I assume there are good reasons that it's implemented the way it is. Perhaps there was no alternative when it was initially developed? And we're constrained by b

[issue42068] For macOS, package the included Tcl and Tk frameworks in a rational way.

New submission from Marc Culler : Packaging Tcl and Tk within the python framework is a great idea and a big improvement. But the way it is being done is pretty crazy, and makes it unnecessarily difficult to upgrade the version of Tcl/Tk that python is using. That is something which should be