Fred Drake wrote:
This dependency exists because the content-type parsing functions
happened to be available in zope.publisher. I'd be happy to see
things refactored to allow this dependency to be broken.
Do I remember rightly that there's a zope.contenttype these could be
moved to?
On Thu, Feb 21, 2008 at 9:31 AM, Chris Withers [EMAIL PROTECTED] wrote:
Do I remember rightly that there's a zope.contenttype these could be
moved to?
You do, though I didn't. :-)
zope.contenttype is a copy/hack of an older version of the mimetypes
module from Python's standard library.
Fred Drake wrote:
zope.contenttype is a copy/hack of an older version of the mimetypes
module
from Python's standard library. I'm not sure it's a *good* place to
put
the functions, but it's probably better than zope.publisher.
zope.contenttype has only standard library dependencies, which
Laurence,
thanks for the tip, exactly what I needed to know. :-)
-Morten
On Tue, 19 Feb 2008 10:30:29 +, Laurence Rowe [EMAIL PROTECTED] wrote:
See the discussion on plone-dev a while ago, link integrity checking
will make Plone 3.0 broken and dangerous. Worth trying with 2.9.8 at
On Thu, Feb 21, 2008 at 3:10 PM, [EMAIL PROTECTED] wrote:
zope.contenttype has only standard library dependencies, which is an
improvement for me.
For everyone, really.
Renaming that module to be more descriptive too might be good when it is
copied. See attached diff to trunk r79689
