Re: [Python-Dev] Inconsistent nesting of scopes in exec(..., locals())
Joachim B Haga wrote: >> Since changing this would break class definitions, that ain't going to >> happen. Suggestions for how to explain the behaviour more clearly in the >> exec() documentation probably wouldn't hurt though. > > I don't quite see how exec() affects the class definition syntax? I was merely pointing out that running exec() with separate globals and locals namespaces ends up invoking the same underlying machinery as is used to execute a class definition. For the docs suggestions, could you either email that to [email protected], or else create a documentation issue at bugs.python.org? (It will get lost otherwise) Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: Broken link to download (Mac OS X)
On 18/04/2010 15:13, Ronald Oussoren wrote: On 14 Apr, 2010, at 23:37, Michael Foord wrote: On 14/04/2010 23:32, Greg Ewing wrote: Michael Foord wrote: Building Python requires, I believe, the XCode development tools to be installed. Even then, building a full version of Python - with *all* the C extensions that are part of a Python release - is not a trivial task. What's non-trivial about it? I usually find that the normal "./configure; make; make install" sequence works fine without any further intervention. If you want a framework installation you have to read the README and use a couple of extra options, but it still works very smoothly. A build on my machine produces output similar to: Python build finished, but the necessary bits to build these modules were not found: _bsddb dl gdbm imageoplinuxaudiodev ossaudiodev readline spwd sunaudiodev To find the necessary bits, look in setup.py in detect_modules() for the module's name. Failed to build these modules: _tkinter Obviously many of those are not meant to be built and I usually build Python for running the test suite - so I don't care about not having Tkinter. A new user of Python would most certainly care about not having Tkinter. What's the OS version? Do you have a copy of Tcl/Tk in /Library/Frameworks? 10.6.3 and yes I have Tcl and Tk in /Library/Frameworks. How do I determine which versions they are? All the best, Michael Ronald -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: Broken link to download (Mac OS X)
Michael Foord writes: > 10.6.3 and yes I have Tcl and Tk in /Library/Frameworks. How do I > determine which versions they are? You can use "info patchlevel" in tclsh - assuming you're running a tclsh linked to your /Library version (a normal Tcl install puts this in /usr/local/bin I think). Or, tcl.h (in the Headers folder beneath the framework install) has TCL_VERSION and TCL_PATCH_LEVEL defines near the top of the file. Given that your error is a failure to build and not a skip, it sounds like setup is finding Tcl/Tk. From a quick glance, it looks like tkinter may also require the X11 headers (you'd have to have installed X11 separately) - do you have output in your log from what exactly is failing when that module attempts to build? -- David ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: Broken link to download (Mac OS X)
On 24/04/2010 21:34, David Bolen wrote: Michael Foord writes: 10.6.3 and yes I have Tcl and Tk in /Library/Frameworks. How do I determine which versions they are? You can use "info patchlevel" in tclsh - assuming you're running a tclsh linked to your /Library version (a normal Tcl install puts this in /usr/local/bin I think). $ tclsh % info patchlevel 8.5.7 Or, tcl.h (in the Headers folder beneath the framework install) has TCL_VERSION and TCL_PATCH_LEVEL defines near the top of the file. Given that your error is a failure to build and not a skip, it sounds like setup is finding Tcl/Tk. From a quick glance, it looks like tkinter may also require the X11 headers (you'd have to have installed X11 separately) - do you have output in your log from what exactly is failing when that module attempts to build? Hmmm... looks like a 32 / 64 bit issue, which I believe may be the expected result when trying to build on Snow Leopard (?). i686-apple-darwin10-gcc-4.2.1: -framework: linker input file unused because linking not done i686-apple-darwin10-gcc-4.2.1: Tk: linker input file unused because linking not done ld: warning: in /Library/Frameworks//Tcl.framework/Tcl, missing required architecture x86_64 in file ld: warning: in /Library/Frameworks//Tk.framework/Tk, missing required architecture x86_64 in file *** WARNING: renaming "_tkinter" since importing it failed: dlopen(build/lib.macosx-10.4-x86_64-2.7-pydebug/_tkinter.so, 2): Symbol not found: _TclFreeObj Referenced from: /compile/python-trunk/build/lib.macosx-10.4-x86_64-2.7-pydebug/_tkinter.so Expected in: dynamic lookup I think my Tk/Tcl install came from an Activestate installer. Michael -- David ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: Broken link to download (Mac OS X)
Michael Foord writes: > Hmmm... looks like a 32 / 64 bit issue, which I believe may be the > expected result when trying to build on Snow Leopard (?). I think so - I haven't tried a 64-bit build myself, but there's a comment in setup.py indicating that none of the Tcl/Tk framework builds support 64-bit. So I suppose you'd have to build 32-bit if you wanted a working _tkinter. -- David ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: Broken link to download (Mac OS X)
On 24/04/2010 21:50, David Bolen wrote: Michael Foord writes: Hmmm... looks like a 32 / 64 bit issue, which I believe may be the expected result when trying to build on Snow Leopard (?). I think so - I haven't tried a 64-bit build myself, but there's a comment in setup.py indicating that none of the Tcl/Tk framework builds support 64-bit. So I suppose you'd have to build 32-bit if you wanted a working _tkinter. Sorry for my ignorance - how do I force a 32 bit build? Michael -- David ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: Broken link to download (Mac OS X)
On 24/04/2010 22:16, Michael Foord wrote: On 24/04/2010 21:50, David Bolen wrote: Michael Foord writes: Hmmm... looks like a 32 / 64 bit issue, which I believe may be the expected result when trying to build on Snow Leopard (?). I think so - I haven't tried a 64-bit build myself, but there's a comment in setup.py indicating that none of the Tcl/Tk framework builds support 64-bit. So I suppose you'd have to build 32-bit if you wanted a working _tkinter. Sorry for my ignorance - how do I force a 32 bit build? Ok, so the following configure command line works and successfully builds Tkinter: ./configure --prefix=/dev/null --with-pydebug --enable-universalsdk All the best, Michael Foord -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
