Am 25.02.2012, 00:18 Uhr, schrieb Marius Gedminas :
The HTML spec requires that:
"To sum up, conforming user agents must observe the following
priorities when determining a document's character encoding (from
highest priority to lowest):
1. An HTTP "charset" parameter in a "Content-Typ
On Mon, Mar 26, 2012 at 05:38:07PM -0400, Tres Seaver wrote:
> In addition to minimizing "Zope-iness", providing full coverage using
> small, descriptively-named unittests makes the code more maintainable.
> For instance, I expect to build on top of these improved tests as the basis
> for a convers
On Tue, Mar 27, 2012 at 4:54 AM, Charlie Clark
wrote:
> """
> We had bug reports about Web sites sending BOM different from the HTTP
> header.
> """
In other words... "the web" will continue to thrive on hacks and
sniffing data to
support users' expectations in spite of the data on "the web".
I
>
>
>
> """
> It is better to encode your Web pages in UTF-8, and serve them as such. In
> HTTP, the HTTP header has priority, then the meta name contained in HTML.
> Some Web pages have specific encoding. It happens often on the Web that the
> Web page encoding is different from the one specified
Am 27.03.2012, 12:16 Uhr, schrieb Fred Drake :
In other words... "the web" will continue to thrive on hacks and
sniffing data to
support users' expectations in spite of the data on "the web".
I appreciate the motivation (it's not the users' fault the content
provider can't
get it right), it sadd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2012 02:25 AM, Wolfgang Schnerring wrote:
> * Tres Seaver [2012-03-26 23:38]:
>> I've (finally!) finished my work to get zope.interface to 100% unit
>> test coverage without relying on doctests:
>
> That's an impressive feat, congratulations
Hi,
I found out, somewhat surprised, that __parent__ pointers are just
disguised aq_parent pointers.
The changelog entries for zope 2.12 are a bit misleading in this regard.
Is there somewhere an explanation of how this works? I was quite by
some of the properties.
Best regards,
Patrick
On Tue, Mar 27, 2012 at 2:53 PM, Patrick Gerken wrote:
> I found out, somewhat surprised, that __parent__ pointers are just
> disguised aq_parent pointers.
Are you maybe trying to use or set __parent__ on Acquisition wrappers
instead of unwrapped objects?
AQ wrappers have various attributes, amo
On Tue, Mar 27, 2012 at 15:18, Hanno Schlichting wrote:
> On Tue, Mar 27, 2012 at 2:53 PM, Patrick Gerken
> wrote:
>> I found out, somewhat surprised, that __parent__ pointers are just
>> disguised aq_parent pointers.
>
> Are you maybe trying to use or set __parent__ on Acquisition wrappers
> in
On Tue, Mar 27, 2012 at 6:36 AM, Charlie Clark
wrote:
> True but I think that the problem was largely of our own making in not
> coming up with "one, preferably only one" way of handling this. Re-reading
> Marius' post I was struck by the whole idea of the http-server transcoding
> the content on
On Tue, Mar 27, 2012 at 3:50 PM, Patrick Gerken wrote:
> Hmm, since I didn't understand what magic happens with __parent__ pointers,
> I tried the following in pdb:
> unwrapped = aq_base(a)
> unwrapped.__parent__ = aq_base(a.__parent__)
>
> So I stored a not acquisition wrapped object onto the __p
Am 27.03.2012, 16:04 Uhr, schrieb Fred Drake :
Transcoding on the fly?
The page template generates Unicode; that's then encoded.
Are you suggesting we shouldn't be using Unicode as the internal
representation?
Not at all, just harking back to the time when we didn't use unicode
internally.
On Tue, Mar 27, 2012 at 12:36:19PM +0200, Charlie Clark wrote:
> Am 27.03.2012, 12:16 Uhr, schrieb Fred Drake :
>
> >In other words... "the web" will continue to thrive on hacks and
> >sniffing data to support users' expectations in spite of the data on
> >"the web". I appreciate the motivation (
On Mon, Mar 26, 2012 at 05:38:07PM -0400, Tres Seaver wrote:
> I've (finally!) finished my work to get zope.interface to 100% unit test
> coverage without relying on doctests:
>
> http://svn.zope.org/zope.interface/branches/tseaver-better_unittests/
Yay!
> The work is outlined in this document
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2012 05:08 AM, Brian Sutherland wrote:
> On Mon, Mar 26, 2012 at 05:38:07PM -0400, Tres Seaver wrote:
>> In addition to minimizing "Zope-iness", providing full coverage
>> using small, descriptively-named unittests makes the code more
>> maint
On Mon, Mar 26, 2012 at 05:38:07PM -0400, Tres Seaver wrote:
> I've (finally!) finished my work to get zope.interface to 100% unit test
> coverage without relying on doctests:
>
> http://svn.zope.org/zope.interface/branches/tseaver-better_unittests/
>
> The work is outlined in this document on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2012 05:08 AM, Brian Sutherland wrote:
> On Mon, Mar 26, 2012 at 05:38:07PM -0400, Tres Seaver wrote:
>> In addition to minimizing "Zope-iness", providing full coverage
>> using small, descriptively-named unittests makes the code more
>> mai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2012 06:21 PM, Marius Gedminas wrote:
>> $ bin/python setup.py dev
>
> Is that different from 'python setup.py develop'? I've never seen 'dev'
> before.
'dev' is an alias (defined in 'setup.cfg' for the following::
setup.py develop eas
This is the summary for test reports received on the
zope-tests list between 2012-03-26 00:00:00 UTC and 2012-03-27 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2012 06:32 PM, Marius Gedminas wrote:
> I've a comment about this change, which was part of that large "merge
> from launchpad" commit:
>
> ---
> zope.interface/branches/tseaver-better_unittests/src/zope/interface/_zope_interface_coptimiza
20 matches
Mail list logo
