Geek Answers Handbook

What is behind the python package namespaces: z3c, zc, collect?

So, all of them are somehow related to zope. The question is how?

I am not familiar with Zop. I think zc, z3c are behind the Zope Component and Zope3 Component , but I want to be sure. There is also a collective namespace. What packages go under it?

What are other famous python package namespaces?

Are there any conventions when a package should contain names with zc, z3c and others?

Sometimes I see packages starting with zc, and I cannot use rationate why they are put in names. For example, z3c.sqlalchemy has a namespace because it is a sqlalchemy wrapper for zope projects. But another zc.buildout example looks like a completely independent project. Did this namespace just happen because it was developed by people who work on Zope? If I worked on Zope, would that mean I should prefix my projects with zc , even if they are not related to any other Zope package?

+6
python zope
source share
2 answers
  • zc - "Zope Corporation".
  • z3c is a "Zope 3 community", a namespace that has long been "deprecated", i.e. new packages are not created with this namespace.
  • collective is part of Plone Collective, the svn repository for Plone packages with friendly members. This is the default namespace for new common Plone packages that are no longer part of the Plone core.

Also interesting:

  • zope , originally used for packages that were part of Zope 3. Now rarely used for new packages.
  • Products used for older Zope2 / Plone packages. The historical remainder of the fact that all Zope2 products should have been in the Products directory, as there used to be namespace packages.
+8
source share

Stefan Richter and I, where we prototyped some packages on zope sprint that really didn't fit into the zope package namespace. This was the time when we started using z3c as the package name. That should mean the zope 3 community, as Lennart says. But the namespace is not out of date.

The question is probably what kind of license exchange agreement someone likes to use if he likes to make the zope package repository. I think z3c and the collective use of different licensed materials.

Z3c repositories are part of the zope repository and use the same license (ZPL), etc., since zope itself uses. But it also means that you need to be a zope member to use it.

By the way, using z3c or a team outside the respective repositories is probably very bad.

Relationship Roger Inheichen

+1
source share

More articles:


All Articles