[Zope-dev] implementing zope.component 4.0

[Tres Seaver]

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

Martijn Faassen wrote:

> Are people okay with the proposed semantics?

+1.

> Would people be okay with such an upgrade path? Any better ideas?

I would start issuign DeprecationWarnings (yes, I know I'm their worst
fan, but we can't keep BBB here, so warnings are appropriate) for
positional defaults in 3.9.x.

I think we should also document the "don't call" API better (pure
lookup):  there have been use cases for this feature (e.g., "adapt to
scalar / string") floating around for a *long* time now, unsupported.
If that means accepting the zope.registry change Chris proposed, I'm
fine with that.

> Most importantly, any volunteers?

I can help some with this.  Perhaps we should start by fleshing it
*really good docs* (not doctests) for zope.component 4.0, including
careful notes about how to make existing code compatible with both 3.x
and 4.x APIs.



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
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

iEYEARECAAYFAksQLNoACgkQ+gerLs4ltQ7+DwCg1ZklISCMQ66rOa7JPDoH2KwU
8GcAoK0o14wk00CAXu+yNsEbP//NTy2z
=78/b
-----END PGP SIGNATURE-----