[Python-Dev] installation of python on a Zaurus
I'm trying to get Python installed on a Zaurus, running OpenBSD. There are several problems with the basic install, some of which I've fixed, more I haven't. I need a particulare question solved here, so I'm going to ffer in recompense what I'ver learned so far: The configure script seems to know (from internal comments) that _XOPEN_SOURCES must be turned off, but it's not efectively turned off, and the configure script needs to ber edited, else you can't even get the basic build to even begin. I don't know enough abou tocnfigure to offer a correct fix, but this is true (I hand-edited the configure script to turn xopen_sources to "no". What I'm after is the reason why it keeps on telling me (during the build, not during configure) that it can't find my just installed tcl85 and tk85 libs. I have soft-linked them to a more common naming (libtcl.so.1.0 and libtk.so.1.0, which is the same index, just dropping the "85" from the naming, and doing the ldconfig'ing ok) but this doesn't seem to fix it. There is a configure-time thing about UCS-tcl, and I don't know what this is. It IS in configure, I can't even locate the source of the complaint about not finding the tcl libs, it's not in the top level directory anywhere. Appreciate the help. ___ 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] installation of python on a Zaurus
On Sun, Jul 24, 2005, Chuck Robey wrote: > > I'm trying to get Python installed on a Zaurus, running OpenBSD. While python-dev can be a good place to get questions like this answered, many more people read comp.lang.python, and you should ask there, too. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ The way to build large Python applications is to componentize and loosely-couple the hell out of everything. ___ 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] should doc string content == documentation content?
On Sunday 24 July 2005 19:24, Martin Blais wrote: > This ties well with the discussion on Doc-SIG a few months ago about > manual docs vs. in-code docs. If a system could be devised to "pull" > the docstrings into the manual (at appropriate places), the issue of > syncing the docs partially goes away. Yes, it does. Avoiding the maintenance burden is a matter of having only one source for the docs, and doesn't not inform the selection of which place is best in a substantial way. A little though. -Fred -- Fred L. Drake, Jr. ___ 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
[Python-Dev] C api for built-in type set?
Is there a C API for the built-in type set? if not, why not? ___ 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] C api for built-in type set?
On Mon, 2005-07-25 at 16:37, Edward C. Jones wrote: > Is there a C API for the built-in type set? if not, why not? Sadly, no. Because no one's written it yet...? -Barry signature.asc Description: This is a digitally signed message part ___ 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] C api for built-in type set?
[Edward C. Jones] > Is there a C API for the built-in type set? > if not, why not? I decided not to expose the internals until the code was fully evolved. For Py2.5, the underlying implementation is shifting to use its own data structure instead of forwarding everything to dictionaries. That will save a substantial amount of memory and offer a tiny speed boost. See a fully-tested draft implementation in nondist/sandbox/set. Of course, you already know that you can use the PyObject_Call() and its brethren to access sets and set methods. The regular, external set API works pretty well with this approach (many methods accept any iterable). The only inefficiencies that arise are with fine grained methods like __contains__() and add(); even then, it is no less efficient than pure Python. Raymond Hettinger ___ 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] zlib 1.2.3 is just out
[Martin v. L?wis wrote] > Raymond Hettinger wrote: > >>I'd guess this belongs in 2.5, with a possible retrofit for 2.4. > > > > > > +1 on backporting, but that is up to Anthony. > > Correct me if I'm wrong - but there isn't much "porting" to this. > AFAICT, this is only relevant for the Windows build (i.e. which > version is used in the binaries). For the source distribution, there > should be no change (except for PCbuild/readme.txt, which should > reflect the version that is used in the Windows build). FWIW, > this currently talks about 1.2.1. Here is a patch to do this (attached) that works on the trunk and against the Python-2.4.1.tgz source tarball. Shall I check this into the HEAD and release24-maint? Trent -- Trent Mick [EMAIL PROTECTED] Index: PCbuild/readme.txt === RCS file: /cvsroot/python/python/dist/src/PCbuild/readme.txt,v retrieving revision 1.59 diff -u -r1.59 readme.txt --- python/PCbuild/readme.txt 6 Jul 2005 19:34:10 - 1.59 +++ python/PCbuild/readme.txt 26 Jul 2005 00:53:17 - @@ -126,15 +126,15 @@ zlib Python wrapper for the zlib compression library. Get the source code -for version 1.2.1 from a convenient mirror at: +for version 1.2.3 from a convenient mirror at: http://www.gzip.org/zlib/ -Unpack into dist\zlib-1.2.1. +Unpack into dist\zlib-1.2.3. A custom pre-link step in the zlib project settings should manage to -build zlib-1.2.1\zlib.lib by magic before zlib.pyd (or zlib_d.pyd) is +build zlib-1.2.3\zlib.lib by magic before zlib.pyd (or zlib_d.pyd) is linked in PCbuild\. However, the zlib project is not smart enough to remove anything under -zlib-1.2.1\ when you do a clean, so if you want to rebuild zlib.lib -you need to clean up zlib-1.2.1\ by hand. +zlib-1.2.3\ when you do a clean, so if you want to rebuild zlib.lib +you need to clean up zlib-1.2.3\ by hand. bz2 Python wrapper for the libbz2 compression library. Homepage Index: PCbuild/zlib.vcproj === RCS file: /cvsroot/python/python/dist/src/PCbuild/zlib.vcproj,v retrieving revision 1.6 diff -u -r1.6 zlib.vcproj --- python/PCbuild/zlib.vcproj 20 Jul 2004 14:37:48 - 1.6 +++ python/PCbuild/zlib.vcproj 26 Jul 2005 00:53:17 - @@ -21,7 +21,7 @@ ___ 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] zlib 1.2.3 is just out
[Scott David Daniels] I'd guess this belongs in 2.5, with a possible retrofit for 2.4. [Raymond Hettinger] >>> +1 on backporting, but that is up to Anthony. [Martin v. L?wis wrote] >> Correct me if I'm wrong - but there isn't much "porting" to this. >> AFAICT, this is only relevant for the Windows build (i.e. which >> version is used in the binaries). For the source distribution, there >> should be no change (except for PCbuild/readme.txt, which should >> reflect the version that is used in the Windows build). FWIW, >> this currently talks about 1.2.1. [Trent Mick] > Here is a patch to do this (attached) that works on the trunk and > against the Python-2.4.1.tgz source tarball. Shall I check this into the > HEAD and release24-maint? Definitely on HEAD, almost certainly on 24 maint. The slight uncertainty wrt the latter is due to the slim possibility that they also made this version of zlib incompatible in some way. I doubt that, but I haven't tried it. BTW, the NEWS files should add a blurb saying Python moved to a new zlib, under a "Windows" section. ___ 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] zlib 1.2.3 is just out
> [Trent Mick] > > Here is a patch to do this (attached) that works on the trunk and > > against the Python-2.4.1.tgz source tarball. Shall I check this into the > > HEAD and release24-maint? [Tim Peters wrote] > Definitely on HEAD, almost certainly on 24 maint. The slight > uncertainty wrt the latter is due to the slim possibility that they > also made this version of zlib incompatible in some way. I doubt > that, but I haven't tried it. Dunno. All tests in test_zlib pass. > BTW, the NEWS files should add a blurb saying Python moved to a new > zlib, under a "Windows" section. Okay. Trent -- Trent Mick [EMAIL PROTECTED] ___ 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] zlib 1.2.3 is just out
On Tuesday 26 July 2005 11:39, Trent Mick wrote: > Here is a patch to do this (attached) that works on the trunk and > against the Python-2.4.1.tgz source tarball. Shall I check this into the > HEAD and release24-maint? Yes. -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. ___ 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] zlib 1.2.3 is just out
[Anthony Baxter wrote] > On Tuesday 26 July 2005 11:39, Trent Mick wrote: > > Here is a patch to do this (attached) that works on the trunk and > > against the Python-2.4.1.tgz source tarball. Shall I check this into the > > HEAD and release24-maint? > > Yes. Okay, done. Can I say that I've had the pleasure for a long while now at only being afflicted with Subversion and Perforce. We can't move Python CVS to subversion soon enough. Then again with a checkin rate hovering belong one per year... :) HEAD: Checking in dist/src/Misc/NEWS; /cvsroot/python/python/dist/src/Misc/NEWS,v <-- NEWS new revision: 1.1323; previous revision: 1.1322 done Checking in dist/src/PCbuild/readme.txt; /cvsroot/python/python/dist/src/PCbuild/readme.txt,v <-- readme.txt new revision: 1.60; previous revision: 1.59 done Checking in dist/src/PCbuild/zlib.vcproj; /cvsroot/python/python/dist/src/PCbuild/zlib.vcproj,v <-- zlib.vcproj new revision: 1.7; previous revision: 1.6 done release24-maint: Checking in dist/src/Misc/NEWS; /cvsroot/python/python/dist/src/Misc/NEWS,v <-- NEWS new revision: 1.1193.2.66; previous revision: 1.1193.2.65 done Checking in dist/src/PCbuild/readme.txt; /cvsroot/python/python/dist/src/PCbuild/readme.txt,v <-- readme.txt new revision: 1.58.2.1; previous revision: 1.58 done Checking in dist/src/PCbuild/zlib.vcproj; /cvsroot/python/python/dist/src/PCbuild/zlib.vcproj,v <-- zlib.vcproj new revision: 1.6.4.1; previous revision: 1.6 done Trent -- Trent Mick [EMAIL PROTECTED] ___ 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
