Did someone have a look on this error ? Is it a trivial thing, or a local
configuration problem, or is it reproduceable?
(I write in utf-8, and I put # -*- coding: utf-8 -*- in my interfaces.py)
Christophe
Christophe Combelles a écrit :
Hello,
When I put some accentuated character in the doc
Tres Seaver wrote:
[snip]
Unicode XML is not only problematic for streaming. For instance, you
*can't* pass a Unicode string to the libxml2 *at all* , unless you want
a core dump. The API requires that you pass it strings encoded as UTF8.
You can in lxml. :) libxml2 as a C API doesn't even suppo
On Monday 15 January 2007 14:25, Sidnei da Silva wrote:
> 'We've tried to look up an adapter for (ISomething, ITheOther) but
> none was found'
> 'Found an adapter for IFoo, which is a base class for the IBar
> interface requested. No adapter has been found for the most-specific
> interface IBar
Andreas Jung wrote:
--On 15. Januar 2007 22:15:46 +0100 Martijn Faassen
[snip]
I still don't see what should ambiguous with this approach.
Ambiguous in that the string seems to say it's in two encodings at once.
You're then "guessing": you're letting the Python string type trump the
declar
On Tue, Jan 16, 2007 at 08:36:48AM +0100, Christian Theune wrote:
> 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 no
On Tuesday 16 January 2007 08:23, Marius Gedminas wrote:
> explainAdapter is probably a bad name for this. Maybe the whole API is
> bad. Maybe it would be more useful to list all adapters that could
> adapt your object to the desired interface, and list them in the order
> of specificness:
You c
Baiju M wrote:
Log message for revision 72044:
Add zope.app.annotation as a top-level package.
Changed:
A zope.app.annotation/
A zope.app.annotation/branches/
A zope.app.annotation/tags/
A zope.app.annotation/trunk/
-=-
Is it really necessary to create the BBB packages in zo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Andreas Jung wrote:
>>
>> --On 15. Januar 2007 22:15:46 +0100 Martijn Faassen
> [snip]
I still don't see what should ambiguous with this approach.
>>> Ambiguous in that the string seems to say it's in two encodings at onc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christophe Combelles wrote:
> Did someone have a look on this error ? Is it a trivial thing, or a local
> configuration problem, or is it reproduceable?
> (I write in utf-8, and I put # -*- coding: utf-8 -*- in my interfaces.py)
>
> Christophe
>
>
Christophe Combelles a écrit :
When I put some accentuated character in the docstring of an interface
and I want to see the interface doc in
apidoc->interfaces->search->IMyInterface,
I then get a server error:
Here is the full backtrace:
--
2007-01-16T16:58:11 ERROR SiteError
http://l
Chris Withers wrote at 2007-1-14 18:14 +:
> ...
>The problem comes when someone sends you something like:
>
>u''
>
>What should be done then?
We parse the declaration and generate an info element
for it but otherwise ignore it as it has lost its meaning after
the XML has been converted to Uni
Martijn Faassen wrote at 2007-1-15 15:44 +0100:
>
>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
Sidnei da Silva wrote at 2007-1-15 17:25 -0200:
> ...
>The kind of info I'm looking for is something along the lines:
>
> 'We've tried to look up an adapter for (ISomething, ITheOther) but
>none was found'
> 'Found an adapter for IFoo, which is a base class for the IBar
>interface requested. No a
Tres Seaver wrote at 2007-1-15 16:57 -0500:
> ...
>Frankly, I don't get the desire to *store* a complete XML document (as
>opposed to the extracted contents of attributes or nodes) as unicode
My desire comes from the easy principle: all text should be unicode.
Decoding/encoding happens only at th
Tres Seaver wrote at 2007-1-16 10:39 -0500:
> ...
>As you speculated, this is actually my preference, except that I don't
>see the need to in scenario D to recode the data and strip the prolog
>encoding attribute. Why wouldn't we just use the XML template's own
>declared encoding to encode any dat
Hi,
Am Dienstag, den 16.01.2007, 20:28 +0100 schrieb Dieter Maurer:
> Sidnei da Silva wrote at 2007-1-15 17:25 -0200:
> > ...
> >The kind of info I'm looking for is something along the lines:
> >
> > 'We've tried to look up an adapter for (ISomething, ITheOther) but
> >none was found'
> > 'Found
Christophe Combelles wrote:
Did someone have a look on this error ? Is it a trivial thing, or a
local configuration problem, or is it reproduceable?
(I write in utf-8, and I put # -*- coding: utf-8 -*- in my interfaces.py)
You must use unicode docstrings. The encoding declaration at the top of
Hi,
I was updating one of the proposals in this minutes and had a somewhat
hard time to define a goal. I stumbled over the upcoming problem of
defining the Zope 3 core and came up with this footnote for myself:
Maybe this can be used as a spark to spur some discussion about the term
'Zope 3 core
Dieter Maurer wrote:
Martijn Faassen wrote at 2007-1-15 15:44 +0100:
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
Tres Seaver wrote:
[snip]
The "just store the XML" scenario is in surprisingly nice. It only needs
attention to encoding and decoding in the always complicated ZPublisher
direct output scenario, and in the edit form scenario.
As you speculated, this is actually my preference, except that I don
Zope 3 has that as well. However, this only gives you the information of
the stack. It doesn't give you information created during the run of
e.g. loops, which I imagine would be interesting to create a trail of
"what did you do?" information.
Well, you could set a list into __traceback_info__ a
I've been working with z3c.zalchemy for a short while, and was finding
it very hard to get started until Stephan Richter gave me a simple
example to work with. In the course of my subsequent investigations, I
found and fixed a few bugs in the ZAlchemy code, and produced a few
simple demos.
With Ju
I've submitted some new tests and a fix for
zope.app.interface.PersistentInterfaceClass in:
http://www.zope.org/Collectors/Zope3-dev/747
I have commit priveleges to the svn repo, but I'd love to get some
review before commiting. baijum from #zope3-dev suggested I post
here. Below is a copy of t
23 matches
Mail list logo
