Hi there, I've uploaded lxml 0.9 eggs for both Windows (thanks Steve Howe) and Mac OS X (thanks Georges Racinet) to the Python cheeseshop. The source is there now too: http://cheeseshop.python.org/pypi/lxml/0.9 Thanks everybody! Oh, we should update INSTALL.txt to have a link to the cheeseshop as well. Regards, Martijn
Martijn Faassen a écrit :
Hi there,
I've uploaded lxml 0.9 eggs for both Windows (thanks Steve Howe) and Mac OS X (thanks Georges Racinet) to the Python cheeseshop. The source is there now too:
http://cheeseshop.python.org/pypi/lxml/0.9
Thanks everybody! Oh, we should update INSTALL.txt to have a link to the cheeseshop as well.
I cannot see the windows egg, are you sure you did upload it ? -- Olivier
Olivier Grisel wrote:
Martijn Faassen a écrit :
Hi there,
I've uploaded lxml 0.9 eggs for both Windows (thanks Steve Howe) and Mac OS X (thanks Georges Racinet) to the Python cheeseshop. The source is there now too:
http://cheeseshop.python.org/pypi/lxml/0.9
Thanks everybody! Oh, we should update INSTALL.txt to have a link to the cheeseshop as well.
I cannot see the windows egg, are you sure you did upload it ?
Heh, I just realized I didn't upload it and came to this mailing list nobody had noticed yet. You're right! I shall look whether I actually have a windows egg and upload it when I find it. :) Meanwhile there's a link on the installation page on our website that links to windows versions. Regards, Martijn
That's great news, but I don't see the Windows egg either.
--Dethe
On 3/21/06, Martijn Faassen
Hi there,
I've uploaded lxml 0.9 eggs for both Windows (thanks Steve Howe) and Mac OS X (thanks Georges Racinet) to the Python cheeseshop. The source is there now too:
http://cheeseshop.python.org/pypi/lxml/0.9
Thanks everybody! Oh, we should update INSTALL.txt to have a link to the cheeseshop as well.
Regards,
Martijn
_______________________________________________ lxml-dev mailing list lxml-dev@codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev
Dethe Elza wrote:
That's great news, but I don't see the Windows egg either.
You're right, I was fooling myself in thinking I had a windows egg. Instead we do have a windows build, linked from here: http://codespeak.net/lxml/installation.html It'd be nice if Steve could make my unreality true by donating a Windows egg. :) Regards, Martijn
Hello Martijn, Tuesday, March 21, 2006, 8:03:29 PM, you wrote:
Dethe Elza wrote:
That's great news, but I don't see the Windows egg either. You're right, I was fooling myself in thinking I had a windows egg. Instead we do have a windows build, linked from here: http://codespeak.net/lxml/installation.html It'd be nice if Steve could make my unreality true by donating a Windows egg. :) Sure, what should I do ? Is there some setuptools script I could base on ? I have no knowledge about it, it would take some time if I had to discover everything myself...
-- Best regards, Steve mailto:howe@carcass.dhs.org
Hello Steve, Tuesday, March 21, 2006, 10:26:27 PM, you wrote:
Sure, what should I do ? Is there some setuptools script I could base on ? I have no knowledge about it, it would take some time if I had to discover everything myself... Nevermind, I found it out. The egg is in here:
http://carcass.dhs.org/lxml-0.9-py2.4-win32.egg It is untested; someone please do it. -- Best regards, Steve mailto:howe@carcass.dhs.org
Steve Howe wrote:
Hello Steve,
Tuesday, March 21, 2006, 10:26:27 PM, you wrote:
Sure, what should I do ? Is there some setuptools script I could base on ? I have no knowledge about it, it would take some time if I had to discover everything myself...
Nevermind, I found it out. The egg is in here:
http://carcass.dhs.org/lxml-0.9-py2.4-win32.egg
It is untested; someone please do it.
Great! I'll upload it to the cheeseshop so it gets some test coverage. :) Regards, Martijn
Martijn Faassen wrote:
Steve Howe wrote:
Hello Steve,
Tuesday, March 21, 2006, 10:26:27 PM, you wrote:
Sure, what should I do ? Is there some setuptools script I could base on ? I have no knowledge about it, it would take some time if I had to discover everything myself...
Nevermind, I found it out. The egg is in here:
http://carcass.dhs.org/lxml-0.9-py2.4-win32.egg
It is untested; someone please do it.
Great!
I'll upload it to the cheeseshop so it gets some test coverage. :)
I just uploaded it, so please Windows users test it out. One thing I noticed is that it's significantly smaller than the mac or linux egg for some reason. Perhaps that's just a compiler producing more compact binaries. Regards, Martijn
Hello Martijn, Wednesday, March 22, 2006, 6:58:16 AM, you wrote:
I just uploaded it, so please Windows users test it out. One thing I noticed is that it's significantly smaller than the mac or linux egg for some reason. Perhaps that's just a compiler producing more compact binaries. Probably because it is dynamically linked, while on linux it is statically linked against libxml/libxslt ?....
-- Best regards, Steve mailto:howe@carcass.dhs.org
On Mar 22, 2006, at 11:19 AM, Steve Howe wrote:
Hello Martijn,
Wednesday, March 22, 2006, 6:58:16 AM, you wrote:
I just uploaded it, so please Windows users test it out. One thing I noticed is that it's significantly smaller than the mac or linux egg for some reason. Perhaps that's just a compiler producing more compact binaries. Probably because it is dynamically linked, while on linux it is statically linked against libxml/libxslt ?....
But I've seen on MacOSX that these libs are dynamically linked. There shouldn't be any difference in a Linux setup. Regards, --------- Georges Racinet Nuxeo SAS gracinet@nuxeo.com http://nuxeo.com Tel: +33 (0) 1 40 33 71 73
Steve Howe a écrit :
Hello Martijn,
Wednesday, March 22, 2006, 6:58:16 AM, you wrote:
I just uploaded it, so please Windows users test it out. One thing I noticed is that it's significantly smaller than the mac or linux egg for some reason. Perhaps that's just a compiler producing more compact binaries. Probably because it is dynamically linked, while on linux it is statically linked against libxml/libxslt ?....
AFAIK it's not the case on linux: ogrisel@groyours:~/Desktop/lxml-0.9-py2.4-linux-i686.egg_FILES/lxml $ ldd etree.so linux-gate.so.1 => (0xffffe000) libxslt.so.1 => /usr/lib/libxslt.so.1 (0xb7f1b000) libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb7e0d000) libz.so.1 => /usr/lib/libz.so.1 (0xb7df9000) libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7dd7000) libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7dc5000) libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7c96000) libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7c92000) /lib/ld-linux.so.2 (0x80000000) By stripping etree.so we can gain more than 50% in size: $ ls -hl etree.so -rw-r--r-- 1 ogrisel ogrisel 1014K 2006-03-21 11:17 etree.so $ strip etree.so $ ls -hl etree.so -rw-r--r-- 1 ogrisel ogrisel 452K 2006-03-22 11:27 etree.so -- Olivier
Martijn Faassen wrote:
Steve Howe wrote:
I just uploaded it, so please Windows users test it out. One thing I noticed is that it's significantly smaller than the mac or linux egg for some reason. Perhaps that's just a compiler producing more compact binaries.
Both are dynamically linked, but maybe etree.so is stripped in the windows version? I just downloaded the Linux/i686 egg and the etree.so in there looks huge (1MB). When stripped, it jumps down to some 400K. Maybe you can rebuild it (with suitable CFLAGS, possibly -Os), then strip it and run the upload again so that it gets a little smaller. Just run CFLAGS="choose me" python setup.py bdist_egg strip build/*/lxml/etree.so python setup.py bdist_egg upload The last command will not rebuild the extension, just upload it. I just did that for an x86-64 egg. Oh, and: you have to remove the original upload via the web interface before you can replace the file. Stefan
participants (6)
-
Dethe Elza -
Georges Racinet -
Martijn Faassen -
Olivier Grisel -
Stefan Behnel -
Steve Howe