Closed cleberjsantos closed 9 years ago
Never pin in setup.py please
Okay, then it is necessary this information in the documentation ;)
hi, I pointed that out into README but in my branch for mail queuing
https://github.com/collective/Products.EasyNewsletter/tree/plone3_queued_mail#requirements
Actually I was expecting for someone to say something about this pull request https://github.com/collective/Products.EasyNewsletter/pull/14
BTW, what the policy (if any) in this case?
I don't understand the question. The policy is your addon must work in at least two last versions of Plone, do not pin something in the setup.py, write it somewhere (in a blog post to find it with google or in the readme)
you get me wrong :) And I'm asking in the wrong place, I know :) Anyway, I was talking about 'merging policy', in the sense that I don't know if I can merge my branch (or any other one) into the master without having any minimal code/feature review.
obsolete - no longer used.
i got it wrong, its used by stoneagehtml - but today version 1.0 works fine with latest stoneagehtml
It is necessary to pin cssutils to version 0.9.7 (either on versions.cfg or in your setup.py)