[lxml-dev] lxml 1.1.1 win32 builds for 2.4 and 2.5

Hello, The builds are up at the usual location: http://puggy.symonds.net/~ashish/downloads/ Please note that the requirement for linking in wsock32.lib is still present in both 2.4 and 2.5. It should at least be mentioned as a possible requirement in the documentation. Regards, ashish

Since this thread is about Windows builds, I thought it would be nice to mention that I'm in the process of setting up a build slave on Windows 2003 to test lxml with Python 2.5 and trunk. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

Hi Sidnei, Sidnei da Silva wrote:
Way cool! How is the build triggered? Note that you can monitor check-ins via a mailing list: http://codespeak.net/mailman/listinfo/lxml-checkins Is the build result publicly available? Stefan

On Fri, Sep 22, 2006 at 07:17:50PM +0200, Stefan Behnel wrote: | Way cool! How is the build triggered? Anytime a checkin is made to python2.5 or trunk. | Note that you can monitor check-ins via | a mailing list: | | http://codespeak.net/mailman/listinfo/lxml-checkins | | Is the build result publicly available? You mean the built binary or the build logs? We could possibly email it somewhere too. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

On Fri, Sep 22, 2006 at 01:58:10PM -0300, Sidnei da Silva wrote: | Since this thread is about Windows builds, I thought it would be nice | to mention that I'm in the process of setting up a build slave on | Windows 2003 to test lxml with Python 2.5 and trunk. One question though: - Should I test the latest release or 'trunk'? Opinions? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

Hi Sidnei, Sidnei da Silva wrote:
well, any problem with testing both? I mean, you can compile "branch/lxml-1.1" and "trunk" independently. Or, if you manage to make it commit-mail triggered, you can see in the mail where the commit was ("lxml/trunk/..." or "lxml/branch/...") and then trigger only the corresponding build. Don't know how much work it would be to set that up, though... Could you give us some more detail how this will work? Stefan

On Sun, Sep 24, 2006 at 05:36:23PM +0200, Stefan Behnel wrote: | well, any problem with testing both? Other than the time required to set it up, nope. | I mean, you can compile "branch/lxml-1.1" | and "trunk" independently. Actually I was refering to tarball. But if we use the branch instead then I agree that not much extra work is needed. Maybe if I can do 'easy_install lxml=1.1 develop' (or whatever is the right incantation) and get a branch checkout? That would be a ton easier. | Or, if you manage to make it commit-mail triggered, | you can see in the mail where the commit was ("lxml/trunk/..." or | "lxml/branch/...") and then trigger only the corresponding build. Don't know | how much work it would be to set that up, though... I will ask Grig. | Could you give us some more detail how this will work? http://www.python.org/dev/buildbot/community/trunk/ http://www.python.org/dev/buildbot/community/2.5/ Look for 'x86 Windows 2003'. Right now the second 'test' step is running an empty test.bat script. I need to fill that with whatever it takes to do a checkout, build and test for lxml for whatever branches should be tested with python 2.5 and trunk (2.6). The test runs will be triggered by python checkins for now, and potentially can be extended to run on lxml checkins too. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

Hi Sidnei, Sidnei da Silva wrote:
Cool, that would allow us to see if anything breaks in the stable series or the development version. And if the builds were up on the web or in an ftp directory somewhere, we could simply point windows users there if they want to test a bug fix and the like.
A simple "svn up" should do the trick after having checked out the respective SVN directory once.
Sadly, cheeseshop can't handle this. But SVN access should work just fine.
That would be cd HD\path\to\lxml-checkout svn up HD\path\to\specific\python setup.py build_ext -i HD\path\to\specific\python test.py If you want, you can also add a HD\path\to\specific\python setup.py bdist_egg at the end to additionally test the egg build.
That should even be enough. As Python checkins tend to happen much more frequently than lxml checkins, lxml will also be rebuilt just a while after the last checkin. Stefan

Stefan Behnel wrote:
You can kind of manage this. You need a link like this (possibly in the long_description that gets put on the Cheese Shop): http://codespeak.net/svn/lxml/branch/threading#egg=lxml-threading Then you can do: easy_install -e -b . lxml==threading And it will check out (as "editable": -e) the branch. You'll have to do "python setup.py develop" on your own after that. -- Ian Bicking | ianb@colorstudy.com | http://blog.ianbicking.org

Since this thread is about Windows builds, I thought it would be nice to mention that I'm in the process of setting up a build slave on Windows 2003 to test lxml with Python 2.5 and trunk. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

Hi Sidnei, Sidnei da Silva wrote:
Way cool! How is the build triggered? Note that you can monitor check-ins via a mailing list: http://codespeak.net/mailman/listinfo/lxml-checkins Is the build result publicly available? Stefan

On Fri, Sep 22, 2006 at 07:17:50PM +0200, Stefan Behnel wrote: | Way cool! How is the build triggered? Anytime a checkin is made to python2.5 or trunk. | Note that you can monitor check-ins via | a mailing list: | | http://codespeak.net/mailman/listinfo/lxml-checkins | | Is the build result publicly available? You mean the built binary or the build logs? We could possibly email it somewhere too. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

On Fri, Sep 22, 2006 at 01:58:10PM -0300, Sidnei da Silva wrote: | Since this thread is about Windows builds, I thought it would be nice | to mention that I'm in the process of setting up a build slave on | Windows 2003 to test lxml with Python 2.5 and trunk. One question though: - Should I test the latest release or 'trunk'? Opinions? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

Hi Sidnei, Sidnei da Silva wrote:
well, any problem with testing both? I mean, you can compile "branch/lxml-1.1" and "trunk" independently. Or, if you manage to make it commit-mail triggered, you can see in the mail where the commit was ("lxml/trunk/..." or "lxml/branch/...") and then trigger only the corresponding build. Don't know how much work it would be to set that up, though... Could you give us some more detail how this will work? Stefan

On Sun, Sep 24, 2006 at 05:36:23PM +0200, Stefan Behnel wrote: | well, any problem with testing both? Other than the time required to set it up, nope. | I mean, you can compile "branch/lxml-1.1" | and "trunk" independently. Actually I was refering to tarball. But if we use the branch instead then I agree that not much extra work is needed. Maybe if I can do 'easy_install lxml=1.1 develop' (or whatever is the right incantation) and get a branch checkout? That would be a ton easier. | Or, if you manage to make it commit-mail triggered, | you can see in the mail where the commit was ("lxml/trunk/..." or | "lxml/branch/...") and then trigger only the corresponding build. Don't know | how much work it would be to set that up, though... I will ask Grig. | Could you give us some more detail how this will work? http://www.python.org/dev/buildbot/community/trunk/ http://www.python.org/dev/buildbot/community/2.5/ Look for 'x86 Windows 2003'. Right now the second 'test' step is running an empty test.bat script. I need to fill that with whatever it takes to do a checkout, build and test for lxml for whatever branches should be tested with python 2.5 and trunk (2.6). The test runs will be triggered by python checkins for now, and potentially can be extended to run on lxml checkins too. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

Hi Sidnei, Sidnei da Silva wrote:
Cool, that would allow us to see if anything breaks in the stable series or the development version. And if the builds were up on the web or in an ftp directory somewhere, we could simply point windows users there if they want to test a bug fix and the like.
A simple "svn up" should do the trick after having checked out the respective SVN directory once.
Sadly, cheeseshop can't handle this. But SVN access should work just fine.
That would be cd HD\path\to\lxml-checkout svn up HD\path\to\specific\python setup.py build_ext -i HD\path\to\specific\python test.py If you want, you can also add a HD\path\to\specific\python setup.py bdist_egg at the end to additionally test the egg build.
That should even be enough. As Python checkins tend to happen much more frequently than lxml checkins, lxml will also be rebuilt just a while after the last checkin. Stefan

Stefan Behnel wrote:
You can kind of manage this. You need a link like this (possibly in the long_description that gets put on the Cheese Shop): http://codespeak.net/svn/lxml/branch/threading#egg=lxml-threading Then you can do: easy_install -e -b . lxml==threading And it will check out (as "editable": -e) the branch. You'll have to do "python setup.py develop" on your own after that. -- Ian Bicking | ianb@colorstudy.com | http://blog.ianbicking.org
participants (5)
-
Ashish Kulkarni
-
Ian Bicking
-
Sidnei da Silva
-
Sidnei da Silva
-
Stefan Behnel