yuppie wrote:
Hi!
Yves Bastide wrote:
yuppie wrote:
3.) GenericSetup is not tested with non-ASCII UTF-8 site settings.
AFAIK import works, but not export. I consider this a bug.
[...]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf4 in position
20: ordinal not in range(128)
This
Florent Guillaume wrote:
Yves Bastide wrote:
And CPS 3.3 and 3.4 have been using Zope 2.9 since its inception, and
is the only recommended "stable" platform for them.
Though they also flood the console with zLOG deprecation warnings ;-)
(I incrementally patched the worst offenders on my local
Yves Bastide wrote:
And CPS 3.3 and 3.4 have been using Zope 2.9 since its inception, and
is the only recommended "stable" platform for them.
Though they also flood the console with zLOG deprecation warnings ;-)
(I incrementally patched the worst offenders on my local copy, but never
sent the
Florent Guillaume wrote:
And CPS 3.3 and 3.4 have been using Zope 2.9 since its inception, and is
the only recommended "stable" platform for them.
Though they also flood the console with zLOG deprecation warnings ;-)
(I incrementally patched the worst offenders on my local copy, but never
se
Jens Vagelpohl wrote:
On 7 Jun 2006, at 20:24, Andreas Jung wrote:
I have the impression that Zope 2.9 is ignored by most ppl :-)
Absolutely not, I test CMF 2.0 against Zope 2.9 ;)
And CPS 3.3 and 3.4 have been using Zope 2.9 since its inception, and is
the only recommended "stable" platfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7 Jun 2006, at 20:24, Andreas Jung wrote:
--On 7. Juni 2006 20:16:49 +0200 Jens Vagelpohl
<[EMAIL PROTECTED]> wrote:
On 7 Jun 2006, at 18:26, Florent Guillaume wrote:
Is it ok if I change CMF 1.6 (currently in beta) to use the logging
mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7 Jun 2006, at 18:26, Florent Guillaume wrote:
Is it ok if I change CMF 1.6 (currently in beta) to use the logging
module instead of zLOG?
zLOG spouts lots of warnings under Zope 2.10 and this sucks.
Yeah, should be fine. You're using CMF 1.
On Wed, 2006-07-06 at 18:26 +0200, Florent Guillaume wrote:
> Is it ok if I change CMF 1.6 (currently in beta) to use the logging
> module instead of zLOG?
> zLOG spouts lots of warnings under Zope 2.10 and this sucks.
+1
--
Rocky Burt
ServerZen Software -- http://www.serverzen.com
News About
Hi!
Yves Bastide wrote:
yuppie wrote:
2.) GenericSetup explicitly doesn't support non-UTF-8 site settings.
If someone provides a good patch this feature can be added.
But with the problems you mention later ('default_charset',
'management_page_charset', and so on), how would you envision
Florent Guillaume wrote:
Is it ok if I change CMF 1.6 (currently in beta) to use the logging
module instead of zLOG?
zLOG spouts lots of warnings under Zope 2.10 and this sucks.
+1 if you forward port the fixes ;)
(see http://www.zope.org/Collectors/CMF/439)
Cheers, Yuppie
__
Is it ok if I change CMF 1.6 (currently in beta) to use the logging
module instead of zLOG?
zLOG spouts lots of warnings under Zope 2.10 and this sucks.
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
yuppie wrote:
Hi Yves!
Yves Bastide wrote:
GenericSetup has problems handling non-ASCII data.
1.) GenericSetup explicitly doesn't support non-UTF-8 XML in profiles.
UTF-8 is the default encoding for XML and I can't see a need to support
other XML encodings.
As output, right? Agreed.
2
Hi Florent!
Florent Guillaume wrote:
Let's not forget also that the goal in CMF 2 (I think) is to have all
content be unicode strings, never encoded ones. In that case
GenericSetup only has to deal with the XML file's encoding (always UTF-8
anyway) but that's all.
That's a long term goal.
yuppie wrote:
Hi Yves!
Yves Bastide wrote:
GenericSetup has problems handling non-ASCII data.
1.) GenericSetup explicitly doesn't support non-UTF-8 XML in profiles.
UTF-8 is the default encoding for XML and I can't see a need to support
other XML encodings.
2.) GenericSetup explicitly do
Hi Yves!
Yves Bastide wrote:
GenericSetup has problems handling non-ASCII data.
1.) GenericSetup explicitly doesn't support non-UTF-8 XML in profiles.
UTF-8 is the default encoding for XML and I can't see a need to support
other XML encodings.
2.) GenericSetup explicitly doesn't support n
Hi Philipp!
Philipp von Weitershausen wrote:
yuppie wrote:
Should be fixed now: http://svn.zope.org/?rev=68474&view=rev
Simply avoiding the cleanup in Zope 2.8 isn't a proper fix. You should
instead do the following (which works across all Zopes):
from zope.testing.cleanup import CleanU
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
jens
- "CachingPolicyManager: Support OFS.Cache.CacheManager",
[Accepted] http://www.zope.org/Collectors/CMF/408
mhammond
- "Windows Developm
yuppie wrote:
> Jens Vagelpohl wrote:
>> This checkin seems to have broken Zope 2.8-compatibility:
>>
>> http://svn.zope.org/GenericSetup/trunk/tests/common.py?rev=68391&r1=41338&r2=68391
>>
>>
>> Specifically, the line "from zope.testing.cleanup import cleanUp"
>> breaks Zope 2.8, I checked all st
18 matches
Mail list logo
