#67 — Bug in "plone" template creates two packages inside egg
by
Anthony Bosio
—
last modified
Apr 10, 2012 02:24 AM
| State | Unconfirmed |
|---|---|
| Version: | 2.21.2 |
| Area | General |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Anthony Bosio |
| Submitted on | Apr 10, 2012 |
| Responsible |
—
|
| Target release: |
—
|
Using the "plone" template in ZopeSkel 2.21.2 to create an add-on product egg called collective.foo results in a ./collective/foo namespace package and a ./src/collective/foo namespace package.
collective.foo
--------------
-/collective
--/foo
---configure.zcml
---__init__.py [ def initialize(context): ]
---tests.py
-/docs
-/src
--/collective
---__init__.py [ __import__('pkg_resources').declare_namespace(__name__) ]
---/foo
----__init__.py [ empty ]
collective.foo
--------------
-/collective
--/foo
---configure.zcml
---__init__.py [ def initialize(context): ]
---tests.py
-/docs
-/src
--/collective
---__init__.py [ __import__('pkg_resources').declare_namespace(__name__) ]
---/foo
----__init__.py [ empty ]
- Steps to reproduce:
- 1. prompt> zopeskel plone collective.foo
2. Use all defaults for wizard
No responses can be added.
If you can, please log in before submitting a reaction.
