On 15 Jan 2007, at 09:47 , Groszer Adam wrote:
Hello Philipp,
I have one failure here:
testPORTCannotConnect
(zope.app.twisted.ftp.tests.test_zope_ftp.FTPServerPort
DataConnectionTestCaes)
What about that? ignore?
Shrug. Not good. Does that happen with the Zope 3.3 branch checkout
as w
Hello Philipp,
.../repos/main/Zope3/branches/3.3
fails too on the same test.
Buildbot seems to sleep these days. I ran into that with one of by
fixes too.
Monday, January 15, 2007, 10:37:52 AM, you wrote:
> On 15 Jan 2007, at 09:47 , Groszer Adam wrote:
>> Hello Philipp,
>>
>> I have one failure
Philipp von Weitershausen wrote:
u''
What should be done then?
Not sure. We could ignore it or raise an error. I'm inclined to ignore it.
That's what I do too...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
Andreas Jung wrote:
[snip]
[Bernd Dorn]
IMHO it should only accept strings, because in the value should be a xml
string and therefore always has to be encoded in 'utf-8' or in the
encoding specified in the processing instruction.
I disagree with that. Since Zope 3 is supposed to use unicode i
Philipp von Weitershausen wrote:
[snip]
A workaround inside parseString() would to check for unicode
and convert the string on-the-fly to a Python string with utf-8 encoding.
This is possibly a limitation of the underlying Expat parser...any
recommendation how to deal with this issue?
Fixed it
--On 15. Januar 2007 13:26:16 +0100 Martijn Faassen
<[EMAIL PROTECTED]> wrote:
How would you propose to parse the following unicode string?
u""
If your parser is unicode-aware then the encoding of the preamble
does not matter since you have already unicode internally and can process
you
On 15 Jan 2007, at 11:02 , Adam Groszer wrote:
Hello Philipp,
.../repos/main/Zope3/branches/3.3
fails too on the same test.
Buildbot seems to sleep these days. I ran into that with one of by
fixes too.
Monday, January 15, 2007, 10:37:52 AM, you wrote:
On 15 Jan 2007, at 09:47 , Groszer Adam w
Hey,
Gmane isn't updating so I can't really reply to the message (not visible
in gmane) that I want to, but I saw the following solution proposed:
def ourparse(text):
if isinstance(text, unicode):
text = text.encode('UTF-8')
xml_parser.parse(text)
now consider what will happen if
--On 15. Januar 2007 14:52:42 +0100 Martijn Faassen
<[EMAIL PROTECTED]> wrote:
Hey,
Gmane isn't updating so I can't really reply to the message (not visible
in gmane) that I want to, but I saw the following solution proposed:
def ourparse(text):
if isinstance(text, unicode):
tex
On Monday 15 January 2007 13:23, Philipp von Weitershausen wrote:
> On 15 Jan 2007, at 11:02 , Adam Groszer wrote:
> > Hello Philipp,
> >
> > .../repos/main/Zope3/branches/3.3
> > fails too on the same test.
> > Buildbot seems to sleep these days. I ran into that with one of by
> > fixes too.
> >
>
On 15 Jan 2007, at 15:15 , Michael Kerrin wrote:
On Monday 15 January 2007 13:23, Philipp von Weitershausen wrote:
On 15 Jan 2007, at 11:02 , Adam Groszer wrote:
Hello Philipp,
.../repos/main/Zope3/branches/3.3
fails too on the same test.
Buildbot seems to sleep these days. I ran into that wit
Hello Michael,
Win32, looking into that...
Monday, January 15, 2007, 3:15:25 PM, you wrote:
> On Monday 15 January 2007 13:23, Philipp von Weitershausen wrote:
>> On 15 Jan 2007, at 11:02 , Adam Groszer wrote:
>> > Hello Philipp,
>> >
>> > .../repos/main/Zope3/branches/3.3
>> > fails too on the
Hey,
On 1/15/07, Andreas Jung <[EMAIL PROTECTED]> wrote:
[snip]
ok, got it. But this problem can be solved easily by changing the encoding
within the preamble.
I would say refusing to guess and bailing out with an error message is
better in this case. The Zen of Python:
In the face of ambigui
Adam Groszer wrote:
Buildbot seems to sleep these days.
Indeed. The Windows version tends to fall over and I've been too busy
to notice of late. I wish I had time to try a newer version, but last
time I did that Twisted had removed support for one of the APIs buildbot
uses from their Windo
One of the most common issues that I've faced, and watched several
people struggle with, during Zope 3 development is to figure why a
certain adapter is not found, or why a certain other adapter is found
instead of the one you are expecting.
I was wondering if there is something that could be don
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
>
> --On 14. Januar 2007 18:14:45 + Chris Withers <[EMAIL PROTECTED]>
> wrote:
>
>> Dieter Maurer wrote:
>>> A halfway intelligent parser would accept Unicode when it gets it
>>> and concentrate on the remaining part of its t
Chris Withers wrote:
Philipp von Weitershausen wrote:
u''
What should be done then?
Not sure. We could ignore it or raise an error. I'm inclined to ignore
it.
That's what I do too...
See my post elsewhere in the thread for an example of why this is Not Good.
Regards,
Martijn
_
--On 15. Januar 2007 15:44:01 +0100 Martijn Faassen
<[EMAIL PROTECTED]> wrote:
Hey,
On 1/15/07, Andreas Jung <[EMAIL PROTECTED]> wrote:
[snip]
ok, got it. But this problem can be solved easily by changing the
encoding within the preamble.
I would say refusing to guess and bailing out wit
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
--On 14. Januar 2007 18:14:45 + Chris Withers <[EMAIL PROTECTED]>
wrote:
Dieter Maurer wrote:
A halfway intelligent parser would accept Unicode when it gets it
and concentrate on the remaining part of i
Andreas Jung wrote:
--On 15. Januar 2007 15:44:01 +0100 Martijn Faassen
<[EMAIL PROTECTED]> wrote:
On 1/15/07, Andreas Jung <[EMAIL PROTECTED]> wrote:
[snip]
ok, got it. But this problem can be solved easily by changing the
encoding within the preamble.
I would say refusing to guess and bail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Andreas Jung wrote:
>>> --On 14. Januar 2007 18:14:45 + Chris Withers <[EMAIL PROTECTED]>
>>> wrote:
>>>
Dieter Maurer wrote:
> A halfwa
--On 15. Januar 2007 22:15:46 +0100 Martijn Faassen
<[EMAIL PROTECTED]> wrote:
My point is that:
u"Some non-ascii
text"
is confusing at best. One part of this says it's a unicode string, the
other part says it's in encoding latin-1.
The string above would be used for internal storage but
Am Montag, den 15.01.2007, 17:25 -0200 schrieb Sidnei da Silva:
> One of the most common issues that I've faced, and watched several
> people struggle with, during Zope 3 development is to figure why a
> certain adapter is not found, or why a certain other adapter is found
> instead of the one you
23 matches
Mail list logo
