p4a.plonecalendar defines p4a.ploneevent as dependency in its setup.py
(and has some setup code within p4a.plonecalendar). This is a very
hard-coded
and unnecessary dependency. First, using schemaextender for extending
the schema
of ATEvent site-wide and instance-wide is a pretty big hammer and
second, there is
no way to use p4a.plonecalendar with a custom event implementation
(vs.event derives
from ATEvent) not using recurrence or in a different way. I recommend
that this
dependencies should be removed (separation of concerns) - all ploneevent
related
setup code should be moved into the p4a.ploneevent implementation or at
least the
setup code in p4a.plonecalendar should work without ploneevent. This means:
- remove the p4a.ploneevent dependency from the setup.py
- let the p4a.plonecalendar setup code check if ploneevent is installed
If you want to use p4a.ploneevent, specify it as an explicit dependency
in your
buildout.cfg.
Thoughts?
Andreas
--
ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: in...@zopyx.com - Phone +49 - 7071 - 793376
Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535
Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK
------------------------------------------------------------------------
E-Publishing, Python, Zope & Plone development, Consulting
I agree, this is a mistake.
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
Can you take some time to clean it up as Andreas suggests?
thanks,
Nate
--
Nate Aune - na...@jazkarta.com
http://www.jazkarta.com
Already done.
I hope to make a release this week. I'm waiting for a Norwgian translation. :)