I think we need to have a much more basic discussion.
IMO deprecation was a reasonable thing to try that hasn't really
worked out well. People find deperecation warnings to be very
annoying and I don't think it's going to be practical to make
backward-concompatable changes when eggs are
Jim Fulton wrote:
I think we need to have a much more basic discussion.
IMO deprecation was a reasonable thing to try that hasn't really
worked out well. People find deperecation warnings to be very
annoying and I don't think it's going to be practical to make
Baiju M wrote:
There are few deprecated packages in zope.app namespace, should we
create individual eggs for those packages ?
-1
What about creating a single egg with all deprecated packges ?
+1 :)
If so, what should be the name of that all-deprecated-in-one package name ?
We don't
Jim Fulton wrote:
On Mar 29, 2007, at 6:30 AM, Baiju M wrote:
Hi,
There are few deprecated packages in zope.app namespace, should we
create individual eggs for those packages ?
Yes.
What about creating a single egg with all deprecated packges ?
-1. We should be able to create the