Re: PLEASE don't remove eggs [was Re: [Zope3-dev] faulty releases and pypi access [update]]
On Sep 26, 2007, at 10:35 AM, Jim Fulton wrote: This is also a technical issue: As long as zc.buildout and setuptools foolishly accept dependency links from an egg, it'll be painful to detect accidental reliance on external repositories. That's a good point. I wouldn't go so far as to say foolishly, but I would say that this is a policy that should be overrideable. Checkins to buildout (with tests, of course) accepted. Sort of that, a feature request in launchpad would be helpful so this idea doesn't get forgotten. Jim -- Jim Fulton Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: PLEASE don't remove eggs [was Re: [Zope3-dev] faulty releases and pypi access [update]]
Gary Poster wrote at 2007-9-26 15:47 -0400: ... So, yes, you are right, I stated an extreme position and I could be argued away from the edge. But the extremity of my position is a simple, followable rule that I certainly prefer over the case you describe. Okay, we disagree. Non working releases produce problems for most people downloading them. Thus, if they are out, and no better release is available, get rid of them such that normal users would again get the earlier, better working releases. It may hurt special users (such as maybe you). Be it. -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
PLEASE don't remove eggs [was Re: [Zope3-dev] faulty releases and pypi access [update]]
On Sep 26, 2007, at 4:49 AM, Christian Theune wrote: - Remove the broken files. I'm not sure if this is related, but I noticed yesterday at least of couple of eggs that we are using had been removed, in this case from zope.org. Please, whoever is doing this, stop. If a release is brown-bagged as far as you are concerned for some reason, please do not assume it is ok to delete for others. I should make our own private copies of the eggs we use, to completely isolate us from these sorts of things, but I have not gotten around to it...nor am I thrilled at the prospect of that overhead. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: PLEASE don't remove eggs [was Re: [Zope3-dev] faulty releases and pypi access [update]]
On 9/26/07, Gary Poster [EMAIL PROTECTED] wrote: I should make our own private copies of the eggs we use, to completely isolate us from these sorts of things, but I have not gotten around to it...nor am I thrilled at the prospect of that overhead. This is also a technical issue: As long as zc.buildout and setuptools foolishly accept dependency links from an egg, it'll be painful to detect accidental reliance on external repositories. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: PLEASE don't remove eggs [was Re: [Zope3-dev] faulty releases and pypi access [update]]
On Sep 26, 2007, at 10:10 AM, Fred Drake wrote: On 9/26/07, Gary Poster [EMAIL PROTECTED] wrote: I should make our own private copies of the eggs we use, to completely isolate us from these sorts of things, but I have not gotten around to it...nor am I thrilled at the prospect of that overhead. This is also a technical issue: As long as zc.buildout and setuptools foolishly accept dependency links from an egg, it'll be painful to detect accidental reliance on external repositories. That's a good point. I wouldn't go so far as to say foolishly, but I would say that this is a policy that should be overrideable. Checkins to buildout (with tests, of course) accepted. Jim -- Jim Fulton Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: PLEASE don't remove eggs [was Re: [Zope3-dev] faulty releases and pypi access [update]]
Gary Poster wrote at 2007-9-26 09:39 -0400: ... - Remove the broken files. I'm not sure if this is related, but I noticed yesterday at least of couple of eggs that we are using had been removed, in this case from zope.org. Please, whoever is doing this, stop. If a release is brown-bagged as far as you are concerned for some reason, please do not assume it is ok to delete for others. I do not agree. When I have understood Christian correctly, then these distributions were not working at all (they lacked ZCML files). Distributions not working at all should be deleted as soon as one recognizes they are not working at all -- to limit the damage they may cause. Of course, not having a tag in the SVN repository is not a sufficient reason to remove otherwise fully working distributions again. -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: PLEASE don't remove eggs [was Re: [Zope3-dev] faulty releases and pypi access [update]]
On Sep 26, 2007, at 3:33 PM, Dieter Maurer wrote:
Gary Poster wrote at 2007-9-26 09:39 -0400:
...
- Remove the broken files.
I'm not sure if this is related, but I noticed yesterday at least of
couple of eggs that we are using had been removed, in this case from
zope.org. Please, whoever is doing this, stop. If a release is
brown-bagged as far as you are concerned for some reason, please do
not assume it is ok to delete for others.
I do not agree.
When I have understood Christian correctly, then these distributions
were not working at all (they lacked ZCML files).
Distributions not working at all should be deleted as soon
as one recognizes they are not working at all -- to limit
the damage they may cause.
Of course, not having a tag in the SVN repository is
not a sufficient reason to remove otherwise fully working
distributions again.
If you released some software that does an os.system('rm -rf .') or
something, then, OK, maybe you can convince me. So, yes, I have a
line past which maybe deletion is ok with me.
But I disagree with yours--code is still importable without ZCML
files and I may only be using a given package in that way and relying
on it in my buildouts, not having noticed the lack of zcml because it
is irrelevant to me.
In the vast majority of cases--for instance, in the case of someone
who apparently removed a zope.app.wsgi egg recently--it simply
shouldn't be done.
So, yes, you are right, I stated an extreme position and I could be
argued away from the edge. But the extremity of my position is a
simple, followable rule that I certainly prefer over the case you
describe.
Gary
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
