Tom Loredo added the comment:
Thanks for handling this, Ned! -Tom
--
___
Python tracker
<http://bugs.python.org/issue11217>
___
___
Python-bugs-list mailin
Tom Loredo added the comment:
Ned-
Thanks a lot for the clarifications. Both the tracker and modified
web page have cleared things up for me.
> "* No recommended or alternate Tcl/Tk is indicated for 32/64 on 10.6. But
> the 2.7.2 patched README indicates
> ActiveTcl-8.5.9 wi
Tom Loredo added the comment:
The attached patch does the trick.
--
Added file: http://bugs.python.org/file20792/Python-2.7.1-patch.txt
___
Python tracker
<http://bugs.python.org/issue11
Tom Loredo added the comment:
I believe this is a bug.
The -32 part of Mac/Makefile.in builds and links the -32 versions here:
ifneq ($(LIPO_32BIT_FLAGS),)
lipo $(LIPO_32BIT_FLAGS) -output
$(DESTDIR)$(prefix)/bin/python$(VERSION)-32 pythonw
lipo $(LIPO_32BIT_FLAGS) -output
Tom Loredo added the comment:
I see this is marked as fixed but pending; perhaps the following comment will
be useful.
I encountered the IDLE/Tk instability issue when working on the Homebrew
formula for Python-2.6.5 a year ago (March 2010). Building a universal
framework Python on Intel
Tom Loredo added the comment:
I believe the main Makefile makes the Mac/Makefile.in installunixtools target
automatically, and I don't see that it should do "the right thing" regarding
linking a python-32.
I did the brew install again, logging the output, and adding an
New submission from Tom Loredo :
When building a universal framework Python-2.7.1 with homebrew on 10.6.6,
python-32 (and its target, python2.7-32) are built and installed in the
framework executable path, but they are not linked in /usr/local/bin.
msg101156 in Issue 8089 recognized this as
Tom Loredo added the comment:
> Unless you vehemently disagree, I am not making this a release blocker for
> 2.6.5.
I'm not sure who you are asking (I doubt it was me!), but I don't consider this
a release blocker. The only possible substantive issue is whether "pytho
Tom Loredo added the comment:
> the python-32 executable has never been linked into /usr/local/bin.
What I meant by "the version pointed to" is: The "python" command
in 2.6.4 produced by an "intel" universal build (whether in the
framework or the install pre
Tom Loredo added the comment:
Ned-
I *did* run "make install"; everything I reported was about the situation
*after* running "make install". In particular, I don't know any way to get
access to IDLE without "make install"; what I described came from using
Tom Loredo added the comment:
Attempted to build 2.6.5rc2 on Mac Pro (2006), OS 10.6.2, following
instructions in Mac/README:
./configure --prefix=/usr/local/tmp --enable-framework
--with-universal-archs=intel --enable-universalsdk=/
Results of "make test" are as expected
Tom Loredo added the comment:
> Ronald Oussoren added the comment:
>
> Fix in r78755 (2.7) and r78756 (3.2)
Thanks for your attention to this, Ronald---and all the hard
work on the OS X support.
-Tom
-
This mail sent through
New submission from Tom Loredo :
Build Py-2.7a3 on Snow Leopard OS 10.6.2 with a non-default framework name:
./configure --prefix=/usr/local/tmp --enable-framework
--with-framework-name=PythonAlpha --enable-universalsdk=/
--with-universal-archs=intel
"make" succeeds, "m
13 matches
Mail list logo
