Zope2.12 does not depend on zope.app.container

Bug #450311 reported by Patrick Gerken
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Undecided
Unassigned

Bug Description

Zope2.12 does not depend on zope.app.container.

Lots of existing packages do use this package for the IAdding interface. These packages would all needlessly be broken. zope.app.container already redirects to the up to date interfaces and emits depreceated warnings. Since zope2.12 is so new and 2.11 afaik did contain that packages, it would make sense to list zope.app.container as a dependency and remove it one or two releases later. Then most packages should have updated their dependencies.

Third party packages of course could also update their packages to depend on zope.app.container, but the same time they then could also do all necessary upgrades for zope2.12, which will take some time. Therefor I think it makes more sense to add this dependency to Zope2.12

Revision history for this message
Tres Seaver (tseaver) wrote : Re: [zope2-tracker] [Bug 450311] [NEW] Zope2.12 does not depend on zope.app.container

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Patrick Gerken wrote:
> Public bug reported:
>
> Zope2.12 does not depend on zope.app.container.
>
> Lots of existing packages do use this package for the IAdding interface.
> These packages would all needlessly be broken. zope.app.container
> already redirects to the up to date interfaces and emits depreceated
> warnings. Since zope2.12 is so new and 2.11 afaik did contain that
> packages, it would make sense to list zope.app.container as a
> dependency and remove it one or two releases later. Then most packages
> should have updated their dependencies.
>
> Third party packages of course could also update their packages to
> depend on zope.app.container, but the same time they then could also do
> all necessary upgrades for zope2.12, which will take some time. Therefor
> I think it makes more sense to add this dependency to Zope2.12
>
> ** Affects: zope2
> Importance: Undecided
> Status: New

 status invalid

I'm *strongly* against the idea of "convenience" dependencies: anybody
who needs zope.app.container for some borked third-party package which
doesn't declare it as a dependency can just install it in their
virtualenv, or add it to their buildout.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 <email address hidden>
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrUjc0ACgkQ+gerLs4ltQ4YRACg0SuSBzcuceQadbN8mL9MdPHI
DP0AnA7X2JG2FRGnzc+PJKw7i9Z4vUs+
=NHKs
-----END PGP SIGNATURE-----

Changed in zope2:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.