Stephan Eletzhofer wrote:
> Am 08.06.2009 um 16:13 schrieb Stefan Behnel:
>> Stefan Eletzhofer wrote:
>>> On Mon, Jun 8, 2009 at 7:54 AM, Stefan Behnel wrote:
>>>> What I would like to see is a really fat egg, i.e. one that works on
>>>> hardware platforms supported by MacOS-X. I have no idea how to do that,
>>>> so I can't provide any hints. But since there seem to be some MacOS
>>>> on the list by now, I hope we can get away with some web digging plus
>>>> trial and error.
>>> Well, I don't know if that's possible -- AFAIK there's only "binary
>>> eggs" and that's it.
>> That would be a compiler option, if I'm not mistaken.
> Ah yes -- You mean a mixed PPC/Intel "fat binary" type thing?
>>> So all in all, I think we should identify:
>>> - the LXML versions which are "important enough" to support (1.2.6
>> Since everything before 2.2 is out of maintenance (and the API is mostly
>> compatible across versions anyway), I'd prefer having eggs for 2.2+ only.
>> Providing older eggs will just let people run into ancient bugs.
>>> - the python versions which we support (surely 2.4 and 2.5. what other
>> We currently have Windows eggs for 2.4/5/6 and 3.0, so having the same
>> span for MacOS eggs would be nice.
> u-huh, well :)
> I don't know about 3.0 yet -- let's see if I can build it.
At least lxml currently compiles on 3.0-Py3.1rc1, so if you get 3.x
installed, it should 'just work'.
>>> I could perhaps set up a semi-automated system on my mac server to build
>>> I can also put them on a FTP / Web Server somewhere, and I could (given
>>> access) also upload the static eggs to PyPi.
>> Sure. Do you have a PyPI account?
> Yup: "seletz"
Ok, you have a maintainer role for lxml now.
>>> Do we want to give the static versions a dedicated name?
>>> "lxml-x.y.z-static" or smth like
>>> that? Maybe not everyone wants static eggs (even not on OSX boxen)?
>> I would want them to be the default download on MacOS (i.e. no special
>> naming), but only after some testing by some MacOS users on differently
>> configured systems, i.e. using different MacOS versions, different
>> distributions, different Python versions, etc. So maybe you could provide
>> them separately first?
> Yes sure -- you mean "separately" as in "not on pypi"?
Yep, just build some and advertise them on lxml-dev asking for feedback. If
they seem to work for everyone, we can upload them to PyPI.