Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

plone.namedfile 3.0.6 requirement #1311

Closed
papachoco opened this issue Jan 8, 2016 · 1 comment
Closed

plone.namedfile 3.0.6 requirement #1311

papachoco opened this issue Jan 8, 2016 · 1 comment

Comments

@papachoco
Copy link

Is there any reason why plone.namedfile 3.0.6 requires plone.protect. It seems to be a minor upgrade to introduce a hard dependency on a Plone product. We are currently running w/ a minimum set of deps for plone.namedfile (3.0.5) - (zope and ZODB). Is there any way we could have a release without the plone.protect hard requirement?

Thanks a lot

Carlos
@papachoco papachoco changed the title plone.namedfile requirement plone.namedfile 3.0.6 requirement Jan 8, 2016
thet added a commit to plone/plone.namedfile that referenced this issue Jan 8, 2016
@thet
Make plone.protect a soft dependency. This allows to use this package…
37fa59a 
… in setups without the Plone stack. Fixes plone/Products.CMFPlone#1311
@thet thet mentioned this issue Jan 8, 2016
Merged
@thet
Copy link
Member

thet commented Jan 8, 2016

Not really a big reason, except that no one came across your use case to use plone.namedfile without the Plone stack. You do? Great!

Here is the fix: plone/plone.namedfile#18

Next plone.namedfile release could contain it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thet @papachoco