Author zach.ware
Recipients python-dev, r.david.murray, serhiy.storchaka, terry.reedy, zach.ware
Date 2014-04-14.18:11:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397499100.53.0.477905646858.issue20035@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, debugging again with better breakpoints, I see what I missed before, so here's a new patch that does things a little differently.  This patch sets the TCL_LIBRARY envvar just before calling Tcl_FindExecutable, and unsets it after the call.  The $tcl_library Tcl var is set after interpreter creation, as in the previous patch.  Both places do nothing if TCL_LIBRARY envvar is already set or the Tcl library isn't in one of the two expected locations.

I attempted to get things to work by setting Tcl's encoding search path before the call to Tcl_FindExecutable, but doing so seems to require some part of the initialization done by Tcl_FindExecutable.  I would much prefer a solution that doesn't mess around with the TCL_LIBRARY envvar at all, but I've had no luck with it.
History
Date User Action Args
2014-04-14 18:11:40zach.waresetrecipients: + zach.ware, terry.reedy, r.david.murray, python-dev, serhiy.storchaka
2014-04-14 18:11:40zach.waresetmessageid: <1397499100.53.0.477905646858.issue20035@psf.upfronthosting.co.za>
2014-04-14 18:11:40zach.warelinkissue20035 messages
2014-04-14 18:11:40zach.warecreate