Re: [lxml-dev] lxml 2.0.4 released
René 'Necoro' Neumann wrote:
Just me again :) - what's about the GTK-hang-bug?
Sorry, that fix went missing. I just re-released a new source distro that has it. Sorry for the inconvenience. Stefan
Stefan Behnel wrote:
René 'Necoro' Neumann wrote:
Just me again :) - what's about the GTK-hang-bug?
Sorry, that fix went missing. I just re-released a new source distro that has it.
Please don't do that! I know it's tempting, but released is released, and this should've been 2.0.5 or 2.0.4.1. Releasing two things under the same version number risks quite a bit of confusion. The simple rule is to avoid this under all circumstances. Regards, Martijn
Hi Martijn, Martijn Faassen wrote:
Stefan Behnel wrote:
René 'Necoro' Neumann wrote:
Just me again :) - what's about the GTK-hang-bug? Sorry, that fix went missing. I just re-released a new source distro that has it.
Please don't do that! I know it's tempting, but released is released, and this should've been 2.0.5 or 2.0.4.1. Releasing two things under the same version number risks quite a bit of confusion. The simple rule is to avoid this under all circumstances.
I know, I normally wouldn't do that, sorry. But in this case, there were some 10 minutes between the time I sent the release mail and deleting the source tar from PyPI, and less than 20 minutes before having the fix up. It usually takes a couple of days to weeks to walk up into Debian etc., and I don't expect many people to jump on the train within seconds, so the harm done here should really be negligible... Note also that PyPI presents the MD5 sum of the file, so you can click on that to see if what you have is what you want. Anyway, as I said, you're right in general. Stefan
Hey Stefan, On Tue, Apr 15, 2008 at 1:22 PM, Stefan Behnel <stefan_ml@behnel.de> wrote:
I know, I normally wouldn't do that, sorry. But in this case, there were some 10 minutes between the time I sent the release mail and deleting the source tar from PyPI, and less than 20 minutes before having the fix up. It usually takes a couple of days to weeks to walk up into Debian etc., and I don't expect many people to jump on the train within seconds, so the harm done here should really be negligible...
I know the harm done is probably neglible, but that's only "probably" you still shouldn't do it. :) People who use easy_install or zc.buildout might've hit the 10 minute window and will end up with a slightly different version. People are pulling stuff from the cheeseshop automatically quite frequently these days. Your average Plone buildout includes lxml, for instance.
Note also that PyPI presents the MD5 sum of the file, so you can click on that to see if what you have is what you want. If there is a problem (admittedly unlikely), it might be quite a while before they consider checking MD5 sums.
Anyway, it's up to you, of course. It's just that even while doing this was low-risk, the risk can be entirely eliminated instead. Regards, Martijn P.S. I should add that overall you're doing a most excellent job with lxml, much better than I could've done myself. So this is just a small issue while I actually continue to be blissfully happy. :)
Hi, Martijn Faassen wrote:
People who use easy_install or zc.buildout might've hit the 10 minute window and will end up with a slightly different version. People are pulling stuff from the cheeseshop automatically quite frequently these days. Your average Plone buildout includes lxml, for instance.
You're right. I noticed that 2.1alpha1 was downloaded from PyPI more than a thousand times - within not even three weeks. That's more than every thirty minutes. :) That's even the first time I see four digits for the download counter. Looks like there's a lot going on automatically... BTW, is there a default/required version used in Plone? I'm asking because I was planning to work on a 1.3.7 quite a while ago. It seems that even Ubuntu Hardy will ship with 1.3.6 on board. And there are definitely enough bugs in 1.3.6 to get them fixed in their own right. I just didn't find the time (and incentive) so far to touch that old code again. Stefan
Hi there,
BTW, is there a default/required version used in Plone? I'm asking because I was planning to work on a 1.3.7 quite a while ago. It seems that even Ubuntu Hardy will ship with 1.3.6 on board. And there are definitely enough bugs in 1.3.6 to get them fixed in their own right. I just didn't find the time (and incentive) so far to touch that old code again.
Hm, I think I was mistaken with the plone buildout, as I can't find obvious evidence of it including lxml, but it's quite possible I missed some dependency somewhere. I *know* the Plone people are including lxml with the Windows installer, but that of course won't affect the downloads directly. That said, I certainly have (automatic) dependencies on lxml 1.3.x in some of my applications still. Regards, Martijn
participants (3)
-
Martijn Faassen -
René 'Necoro' Neumann -
Stefan Behnel