Chris McDonough writes:
> I was thinking that too after I did it. ;-) I'll move it to
> Zope.Startup.
Cool. I'll be so bold as to suggest using a separate ZConfig
component instead of sticking the section definition in the main
schema. If you define the section type in warningfilter.xml, imp
On Tue, 2003-11-04 at 12:22, Fred L. Drake, Jr. wrote:
> Chris McDonough writes:
> > Thats where I defined the sectiontype.
>
> I don't think it belongs there; it really has nothing to do with the
> logging.
I was thinking that too after I did it. ;-) I'll move it to
Zope.Startup.
- C
_
Chris McDonough writes:
> Thats where I defined the sectiontype.
I don't think it belongs there; it really has nothing to do with the
logging.
-Fred
--
Fred L. Drake, Jr.
PythonLabs at Zope Corporation
___
Zope-Dev maillist - [EMAIL PROTECTE
On Tue, 2003-11-04 at 12:06, Fred L. Drake, Jr. wrote:
> > It would be nice to have all the config stuff the same on HEAD as on 2.7
> > so we don't run into merge problems later... If we agree and I promise
> > to write a test for the warnfilter, maybe you could just copy the
>
> Have you writt
Chris McDonough writes:
> Oo, oo, Fred. I just checked in a feature on the HEAD only that lets
> you configure Python warning filters using the config file. I think it
> passes Brian's criterion for merge save for any tests.
The MIME types support now passes Brian's criteria; I finally added
Oo, oo, Fred. I just checked in a feature on the HEAD only that lets
you configure Python warning filters using the config file. I think it
passes Brian's criterion for merge save for any tests.
It would be nice to have all the config stuff the same on HEAD as on 2.7
so we don't run into merge p
Brian Lloyd writes:
> fyi, I'm ok with merging this to 2.7 if it already is on the HEAD,
> has tests, and has at least some minimal docs.
It's on the head, and I've performed a check on a running Zope process
that new types specified this way are recognized. I'll check in unit
tests of the lo
L PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Fred L. Drake, Jr.
> Sent: Thursday, October 30, 2003 11:42 PM
> To: robert
> Cc: Zope Developers list; Romain Slootmaekers
> Subject: Re: [Zope-dev] Zope doesn't know enough mime types.
>
>
>
> robert writes:
> &
robert writes:
> would be nice if we had it in 2.7
That's up to Brian Lloyd. I think it's a low-risk change, but we
really want to stabilize and finish 2.7.
-Fred
--
Fred L. Drake, Jr.
PythonLabs at Zope Corporation
___
Zope-Dev maillist -
would be nice if we had it in 2.7
Robert
Am Donnerstag, 30. Oktober 2003 17:50 schrieb Fred L. Drake, Jr.:
> I wrote:
> > Adding some configuration to Zope to identify additional mime.types
> > files to load may be a good idea, and should not be too difficult.
>
> I've done this on the Zope 2 hea
I wrote:
> Adding some configuration to Zope to identify additional mime.types
> files to load may be a good idea, and should not be too difficult.
I've done this on the Zope 2 head; I don't know if it should be ported
to the Zope 2.7 branch.
Zope's configuration file can now have an additiona
Leonardo Rochael Almeida wrote:
Put it in the collector.
http://zope.org/Collectors/Zope/1091
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http:/
Tres Seaver wrote:
On Fri, 2003-10-24 at 09:03, Romain Slootmaekers wrote:
Yo,
Zope doesn't know enough mime types, and there's no easy way to add them
add runtime since you removed the add_type(...) method from mimetypes.py
mime types that spring to mind are:
.ra .ram .rm : audio/x-pn-reala
On Fri, 2003-10-24 at 09:03, Romain Slootmaekers wrote:
> Yo,
>
> Zope doesn't know enough mime types, and there's no easy way to add them
> add runtime since you removed the add_type(...) method from mimetypes.py
>
> mime types that spring to mind are:
>
> .ra .ram .rm : audio/x-pn-realaudio
On Fri, 2003-10-24 at 11:48, Romain Slootmaekers wrote:
> [...]
>
> (Monkey)patching zope(s) to workaround (bugs | missing features) is
> indeed sometimes needed but if the fix is as simple as adding some
> name-value pairs I see no reason why not to do this before the next release.
Put it in
Romain Slootmaekers writes:
> But why the modified mimetypes file has to contain about 40 less
> mime-types than the corresponding file in a python installation from
> python.org is a mistery to me.
The mimetypes module in general has a problem: the known MIME types
are stored in the source
Clemens Robbenhaar wrote:
Hi Romain,
> Yo,
>
> Zope doesn't know enough mime types, and there's no easy way to add them
> add runtime since you removed the add_type(...) method from mimetypes.py
Who is "you" which has removed the function? I guess mimetypes
is a core python module ...
yo
17 matches
Mail list logo
