-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
snip platform / KGS stuff
For the case of *library* packges, rather than platforms, forcing users
into lockstep on dependencies is less desirable.
Example
-
Assume that developer Fred releases a given library
Summary of messages to the zope-tests list.
Period Fri Dec 19 12:00:00 2008 UTC to Sat Dec 20 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Fri Dec 19 20:35:50 EST
Hi Tres
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
[...]
If we that there is a real goal other than future
cleanliness for the deprecation system, then a system which
requries warnings to be explicitly enabled (e.g., via a tool,
or an environment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Ineichen wrote:
Hi Tres
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
[...]
If we that there is a real goal other than future
cleanliness for the deprecation system, then a system which
requries
So, I have a need to put together a more elaborate web page. Lots of
pop-up dialog boxes and dynamically-updated choice lists. How to do that?
I take a look at Pyjamas http://pyjs.org. Pretty cool.
Here's the theory. Write fancy application web page in python using the
Pyjamas/GWT API, then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Washington wrote:
So, I have a need to put together a more elaborate web page. Lots of
pop-up dialog boxes and dynamically-updated choice lists. How to do that?
I take a look at Pyjamas http://pyjs.org. Pretty cool.
Here's the theory.
