On Sun, 2012-12-16 at 22:10 +0100, Godefroid Chapelle wrote:
Le 15/12/12 01:52, Tres Seaver a écrit :
I fixed the remainig issues in persistent and released 4.0.5 today: its
tests properly exercise the C extensions Under Python 3.2 / 3.3.
I want to express my thanks to you, Tres, for
On Thu, 2012-02-02 at 08:46 +0100, Jens Vagelpohl wrote:
Hi Chris,
For what it's worth, in the Pylons Project, we decided to continue
requiring the signing of a contributor's agreement (more or less the
same contributor agreement as Zope requires). But instead of signing
via paper, we
On Wed, 2012-02-01 at 16:29 +0100, Jens Vagelpohl wrote:
On Feb 1, 2012, at 15:53 , Charlie Clark wrote:
Currently the hurdle to getting involved is signing and sending the
committer agreement. A hurdle which I think is worth keeping.
For any code released under the Zope Foundation
On Sat, 2011-12-17 at 21:57 -0500, Chris McDonough wrote:
Hi all,
Is zope.server still largely used by e.g. bluebream, grok, and other
zope 3 apps? Or do people tend to use other WSGI servers instead?
Either way, arguments for or against zope.server would be useful; I'm
trying to decide
On Tue, 2012-01-03 at 07:32 +, Martin Aspeli wrote:
On 3 January 2012 06:39, Chris McDonough chr...@plope.com wrote:
On Mon, 2012-01-02 at 10:39 +, Martin Aspeli wrote:
On 2 January 2012 08:50, Wichert Akkerman wich...@wiggy.net wrote:
On 01/01/2012 08:39 PM, Martin Aspeli wrote
On Mon, 2012-01-02 at 10:39 +, Martin Aspeli wrote:
On 2 January 2012 08:50, Wichert Akkerman wich...@wiggy.net wrote:
On 01/01/2012 08:39 PM, Martin Aspeli wrote:
Hi,
There are three known WSGI implementations of the Zope 2 publisher.
I've had a look at them and made some notes
Hi all,
Is zope.server still largely used by e.g. bluebream, grok, and other
zope 3 apps? Or do people tend to use other WSGI servers instead?
Either way, arguments for or against zope.server would be useful; I'm
trying to decide whether to base some new stuff on it.
- C
Could someone copy the existing zc.buildout-2.0.0a1-py3.2.egg file over
to zc.buildout-2.0.0a1-py3.3.egg on PyPI so it gets shlepped down when
we try to use the Python trunk against existing buildouts?
- C
___
Zope-Dev maillist - Zope-Dev@zope.org
On Mon, 2011-12-05 at 23:47 -0500, Chris McDonough wrote:
These are both odd doctest failures, perhaps also related to the recent
transaction release?
Yes. I'll see if I can fix it in the ZODB trunk.
The ZODB trunk test that failed has been fixed to work with
transaction=1.2.0
On Mon, 2011-12-05 at 15:05 -0500, Chris McDonough wrote:
On Mon, 2011-12-05 at 08:07 +0100, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-12-05 04:02]:
ssh://svn.zope.org/repos/main/zope.configuration/branches/chrism-dictactions
I want to be able to associate
On Mon, 2011-12-05 at 16:21 -0500, Chris McDonough wrote:
Tomorrow, I plan to:
- Merge the chrism-py3 branch of zope.sqlalchemy into its trunk.
(http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/)
to get Python 3 compatibility.
- Once the compat branch is merged, I'll make a 0.7
On Mon, 2011-12-05 at 08:07 +0100, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-12-05 04:02]:
ssh://svn.zope.org/repos/main/zope.configuration/branches/chrism-dictactions
I want to be able to associate a new value (introspectables) with each
ZCML configuration
On Sun, 2011-12-04 at 22:12 -0500, Chris McDonough wrote:
I'm going to make a new major release of the transaction package
tomorrow (without the savepoint release features, and bw incompat with
2.4 and 2.5), unless I hear otherwise.
transaction 1.2.0 released with Py3 compat (and removing
Tomorrow, I plan to:
- Merge the chrism-py3 branch of zope.sqlalchemy into its trunk.
(http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/)
to get Python 3 compatibility.
- Once the compat branch is merged, I'll make a 0.7 release of
zope.sqlalchemy.
Any dissent?
- C
On Mon, 2011-12-05 at 20:31 -0500, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[1]FAILED winbot / ZODB_dev py_254_win32
https://mail.zope.org/pipermail/zope-tests/2011-December/053672.html
This appears to be due to the incompatibility of transaction 1.2 with
ssh://svn.zope.org/repos/main/zope.configuration/branches/chrism-dictactions
Rationale:
I want to be able to associate a new value (introspectables) with each
ZCML configuration action, in support of ZCML support for Pyramid
features described at:
On Wed, 2011-10-12 at 06:07 -0400, Chris McDonough wrote:
On Sat, 2011-10-01 at 03:28 -0400, Chris McDonough wrote:
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
I've added chrism as an owner. Before we make a final release I'd like
to revisit the savepoint release branches
On Sat, 2011-10-01 at 03:28 -0400, Chris McDonough wrote:
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
I've added chrism as an owner. Before we make a final release I'd like
to revisit the savepoint release branches of transaction /
zope.sqlalchemy. I'll bring this up in another
On Mon, 2011-10-10 at 13:14 +0200, Brian Sutherland wrote:
I've managed to port zope.schema to Python 3.2 on a branch
(jinty-python3).
Woo hoo!
It gives up Python 2.5 compatibility and depends on six
(http://packages.python.org/six/). Any objections to me merging this
branch?
Not from me.
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
On 29 September 2011 10:33, Chris McDonough chr...@plope.com wrote:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484view=auto
It is designed to work with Py3k.
I've replaced the bootstrap.py in the chrism-py3 branch
On Mon, 2011-09-26 at 21:47 -0400, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several
tests still fail. I could use some help fixing them.
To run the test suite
On Tue, 2011-09-27 at 06:43 +0100, Chris Withers wrote:
On 27/09/2011 02:47, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several
tests still fail. I could use
On Sun, 2011-09-25 at 23:10 -0400, Stephan Richter wrote:
On Sunday, September 25, 2011, Chris McDonough wrote:
Anyway, it all seems to work given those limitations, but I'm having
trouble making the doctests pass on Python 3. Are there any doctest
ninjas willing to have a look?
Looks
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several
tests still fail. I could use some help fixing them.
To run the test suite:
- Create a Python 3.2 virtualenv.
- Install nose into the
Hi all,
I've ported the transaction package to Python 3 here:
http://svn.zope.org/transaction/branches/chrism-py3/
To get Python 3 support, it ditches 2.4 and 2.5 support, although I may
try to readd 2.5 support.
Anyway, it all seems to work given those limitations, but I'm having
trouble
On Sun, 2011-09-25 at 18:20 -0400, Chris McDonough wrote:
Hi all,
I've ported the transaction package to Python 3 here:
http://svn.zope.org/transaction/branches/chrism-py3/
To get Python 3 support, it ditches 2.4 and 2.5 support, although I may
try to readd 2.5 support.
Anyway
On Fri, 2011-09-23 at 13:05 -0500, Alan Runyan wrote:
please,
can someone create 32/64bit eggs for windows
I think someone needs to kick the wineggbuilder, or at least diagnose
why it's having trouble building eggs for z.i. I'm not sure who's meant
to be running it.
- C
On Thu, 2011-09-22 at 17:25 -0400, Roberto Allende wrote:
Hello
Within PyCon Argentina, Plone Symposium South America and PyCon Brazil
we will run the Caipirinha with Zope Sprint where we'll work on ZTK
components migration to Python3 and to integrate webob with Zope.
Roberto,
Just FYI,
Hi folks,
I've made tags for zope.interface 3.8.0 and zope.component 3.11.0, as
described in a recent thread to this list, but I don't have PyPI owner
rights to publish them. Can someone add me to the owners list for those
packages (my pypi user name is chrism)?
- C
On Thu, 2011-09-22 at 10:10 +0200, Hanno Schlichting wrote:
On Thu, Sep 22, 2011 at 9:03 AM, Chris McDonough chr...@plope.com wrote:
I've made tags for zope.interface 3.8.0 and zope.component 3.11.0, as
described in a recent thread to this list, but I don't have PyPI owner
rights to publish
On Thu, 2011-09-22 at 05:10 -0400, Chris McDonough wrote:
On Thu, 2011-09-22 at 10:10 +0200, Hanno Schlichting wrote:
On Thu, Sep 22, 2011 at 9:03 AM, Chris McDonough chr...@plope.com wrote:
I've made tags for zope.interface 3.8.0 and zope.component 3.11.0, as
described in a recent thread
On Fri, 2011-09-09 at 00:57 -0400, Chris McDonough wrote:
I mentioned previously that it's not that much of a stretch to put this
code into zope.interface because zope.interface.adapter already defines
registry-ish stuff that possesses most of the same concepts as a
component registry
One of these failures was I *think* due to the fact that zope.interface
didn't have an extras_require entry for tests. I've added one;
we'll see how it goes.
- C
On Fri, 2011-09-16 at 01:00 +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests
debugging efforts.
I've found it to work in the past despite that warning.
On Sat, Sep 10, 2011 at 6:32 PM, Chris McDonough chr...@plope.com wrote:
Hanno,
Could you delete and readd the failed repository enlistments at
https://www.ohloh.net/p/zope/enlistments?page=13
I think
Hanno,
Could you delete and readd the failed repository enlistments at
https://www.ohloh.net/p/zope/enlistments?page=13
I think these are them:
svn://svn.zope.org/repos/main/zope.schema/trunk
svn://svn.zope.org/repos/main/zope.security/trunk
They're preventing Zope stats on ohloh from
On Thu, 2011-09-08 at 09:01 +0200, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-09-06 20:06]:
On Tue, 2011-09-06 at 12:50 +0200, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-09-01 04:27]:
It wouldn't be the end of the world to have the global
On Thu, 2011-09-08 at 13:39 +0200, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-09-08 05:21]:
On Thu, 2011-09-08 at 09:01 +0200, Wolfgang Schnerring wrote:
Yes, I like the idea of a fresh start (or at least proper clean
up) quite a bit. And I'd definitely be up
On Thu, 2011-09-08 at 19:03 -0400, Chris McDonough wrote:
On Thu, 2011-09-08 at 13:39 +0200, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-09-08 05:21]:
On Thu, 2011-09-08 at 09:01 +0200, Wolfgang Schnerring wrote:
Yes, I like the idea of a fresh start (or at least
On Tue, 2011-09-06 at 12:50 +0200, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-09-01 04:27]:
It wouldn't be the end of the world to have the global registry and the
global API live in zope.registry, but it doesn't help Pyramid for it to
be in there, and it probably
On Mon, 2011-09-05 at 09:53 +0200, Hanno Schlichting wrote:
On Mon, Sep 5, 2011 at 1:09 AM, Chris McDonough chr...@plope.com wrote:
I've given Python 3 support to zope.deprecation at
http://svn.zope.org/zope.deprecation/branches/chrism-unittesting/
- Which Python versions is this thing
On Mon, 2011-09-05 at 15:00 +0300, Gediminas Paulauskas wrote:
Great. I've merged my branch into the trunk as per the above.
Apparently I don't have owner access on the thing on PyPI so I can't
make a release. Currently owners of the zope.deprecation package are:
J1m, fdrake, menesis.
Hi all,
I've given Python 3 support to zope.deprecation at
http://svn.zope.org/zope.deprecation/branches/chrism-unittesting/
Outstanding questions before I merge:
- Which Python versions is this thing meant to support? I have it
functioning under 2.5, 2.6, 2.7 (and 3.2). Do we need it
to
On Wed, 2011-08-31 at 10:59 +0200, Hanno Schlichting wrote:
On Wed, Aug 31, 2011 at 9:17 AM, Wolfgang Schnerring w...@gocept.com wrote:
Splitting zope.configuration into core mechanics and ZCML support
makes a lot of sense to me.
So, +1 from me.
+1 here too
It turns out that we were
On Thu, 2011-09-01 at 09:15 +0200, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-08-30 03:51]:
On Tue, 2011-08-30 at 08:47 +0200, Wolfgang Schnerring wrote:
My interpretation of your suggestion is that maybe that zope.component
end up as what zope.registry is now
On Thu, 2011-09-01 at 09:22 -0400, Jim Fulton wrote:
On Thu, Sep 1, 2011 at 4:27 AM, Chris McDonough chr...@plope.com wrote:
...
- zope.testing (for addCleanUp of the global registry in
z.c.globalregistry and other places)
This particular detail should simply be cleaned up by
moving
On Tue, 2011-08-30 at 08:47 +0200, Wolfgang Schnerring wrote:
* Chris McDonough chr...@plope.com [2011-08-26 13:27]:
So I'd like to propose to do the split the other way around: Not
extract the core into something else and leave only a hollowed-out
shell of integration and miscellany
Rationale
Like the previous proposal by Tres Seaver related to
zope.component, this is a step that
will help port crucial Pyramid dependencies to Python3:
https://github.com/Pylons/pyramid/wiki/Python-3-Porting
At the end of this year's US PyCon, Lennart Regebro described
the
On Thu, 2011-08-25 at 08:50 +0200, Wolfgang Schnerring wrote:
However, I feel that this extraction of the registry bits is a little
too mechanical, and I'd like us to think a little bit about
alternative approaches before we commit this.
I envision the ZTK packages (like zope.component) to
On Tue, 2011-08-09 at 11:48 -0400, Zvezdan Petkovic wrote:
On Aug 8, 2011, at 4:44 PM, Chris McDonough wrote:
Kudos to whomever turned the transaction package's transaction manager
into a context manager and was thoughtful enough to provide the attempts
method (which returns a separate
Kudos to whomever turned the transaction package's transaction manager
into a context manager and was thoughtful enough to provide the
attempts method (which returns a separate context manager, wrapping
the txn context manager, and retries some number of configurable times).
This makes writing
I'm pondering making a release of zope.i18nmessageid to PyPI. It has C
extensions. If I upload the release, does the wineggbuilder still come
along and push windows binary eggs up eventually?
- C
___
Zope-Dev maillist - Zope-Dev@zope.org
On Sun, 2011-07-03 at 17:44 +0200, Hanno Schlichting wrote:
I don't have any skin in this game, but FTR, Mike Bayer isn't feeling
all that confident about Beaker's sessioning component (or so he has
told me). Beaker was originally made as a caching component, and had
sessioning jammed
On Sun, 2011-07-03 at 03:41 +0200, Hanno Schlichting wrote:
- Continue to remove functionality tailored for TTW development, like
SiteRoot, AccessRules, HelpSys and step-by-step most of the ZMI
- Document and use the WSGI publisher and remove obsoleted
functionality like the virtual host
On Mon, 2011-06-13 at 10:08 +0100, Chris Withers wrote:
On 12/06/2011 21:48, Chris McDonough wrote:
Currently if you ask a registry to singly-adapt an object to an
interface, and the object you're trying to adapt implements that
interface, here's what happens:
from
Currently if you ask a registry to singly-adapt an object to an
interface, and the object you're trying to adapt implements that
interface, here's what happens:
from zope.component.registry import Components
c = Components()
from zope.interface import Interface, implements
class
On Mon, 2011-03-21 at 15:53 +0100, Lennart Regebro wrote:
On Mon, Mar 21, 2011 at 15:28, Jim Fulton j...@zope.com wrote:
This might be OK for @implements and maybe @adapts, which describe
behavior, but start feeling wonky to me for something like: @utility.
Well, the wonkyness comes from
On Mon, 2011-03-21 at 14:13 -0400, Jim Fulton wrote:
On Mon, Mar 21, 2011 at 12:59 PM, Chris McDonough chr...@plope.com wrote:
On Mon, 2011-03-21 at 15:53 +0100, Lennart Regebro wrote:
...
It's easy and clear, but has the drawback of encouraging that
registration is done on import time
On Sun, 2011-03-13 at 09:13 +0100, Christian Theune wrote:
Hi Guys,
On 02/10/2011 07:07 AM, Christian Theune wrote:
Hi,
I'll be at PyCon during the sprints. As promised from the tasks last
year, I'd be happy to organize Zope sprinting activity.
Who's coming? Who's interested? Any
are here:
http://docs.pylonsproject.org/projects/pyramid/1.0/narr/advconfig.html
On Tue, 2010-12-07 at 15:32 -0500, Chris McDonough wrote:
On Tue, 2010-12-07 at 14:27 -0500, Chris McDonough wrote:
[13:48] mcdonc override is exactly the wrong phrase to use in the name
of this directive
[13
On Wed, 2010-12-22 at 09:43 -0500, Jim Fulton wrote:
This makes it possible to start testing some of the ZTK with PyPy. There
are challenges of course: certain packages, such as zope.interface, use
C extensions and would need to be installed in plain-python mode (if
available).
It is
Thanks for giving it a shot Christian! I always read the meeting notes,
if I didn't participate.
- C
On Tue, 2010-12-21 at 19:46 +0100, Christian Theune wrote:
Hi,
during my holidays I evaluated where I spend my time. I feel that the
weekly IRC meetings in their current form do not foster
I'm trying to decide whether to repurpose the conflict detection in
zope.configuration for non-XML configuration.
zope.configuration has the following resolveConflicts function, which
attempts to resolve action discriminator conflicts.
def resolveConflicts(actions):
Resolve conflicting
Independent of my previous call for discussion about ZCML conflict
resolution, I'm cutting and pasting my side of a discussion about the
ZCML includeOverrides directive from an IRC chat, because it may come
in useful for folks grappling with its behavior. There's not really any
human-consumable
On Tue, 2010-12-07 at 14:08 -0500, Jim Fulton wrote:
On Tue, Dec 7, 2010 at 1:57 PM, Chris McDonough chr...@plope.com wrote:
Independent of my previous call for discussion about ZCML conflict
resolution, I'm cutting and pasting my side of a discussion about the
ZCML includeOverrides
On Tue, 2010-12-07 at 14:27 -0500, Chris McDonough wrote:
[13:48] mcdonc override is exactly the wrong phrase to use in the name
of this directive
[13:51] mcdonc what it boils down to is that you never, ever really
want to use includeOverrides except in your rootmost zcml file
[13
On Tue, 2010-11-09 at 01:21 +0200, Marius Gedminas wrote:
On Mon, Nov 08, 2010 at 03:35:09PM +0100, Brian Sutherland wrote:
I've committed 2 patches to a jinty-mem branch of zope.interface.
Together these patches reduce the startup memory use of my ZTK based
application by 3%. Is that
On Tue, 2010-10-19 at 14:13 -0400, Brian Sullivan wrote:
So I installed 2.11.4 -- the latest that I could find and still the same
issue.
Clockserver is actually built into newer Zopes and needn't be installed
separately. You configure it by adding stuff to your zope.conf file,
eg.:
I made a new release of zope.i18nmessageid (3.5.3) persuant to a
conversation that took place on this list a few weeks ago related to
switching back to overriding build_ext to allow the package to work on
Jython and other CPython platforms.
Would someone be kind enough to build and upload new
Fabio,
Within the last few months you committed the following change to
zope.i18nmessageid:
http://svn.zope.org/zope.i18nmessageid/trunk/setup.py?rev=102497r1=101297r2=102497
The commit message is Fixed the compilation of the C extension with
python 2.6: refactored it as a setuptools Feature.
Thanks for organizing this Alan. Hopefully folks will follow your lead
and contribute. Agendaless put some money into the pot today.
On Thu, 2010-06-24 at 14:19 -0500, Alan Runyan wrote:
The blog: http://zodbdocs.blogspot.com/
I am coordinating an effort to have a ZODB book written by one
On 4/17/10 5:20 PM, Tres Seaver wrote:
- Documentation should be written for documentation's sake. The
emphasis should be on helping people understand what the software is
for and how to use it, *not* on coverage.
Amen.
- Documentation should be executable. Manuel helps a lot for this.
://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
--
Chris McDonough
Agendaless Consulting, Fredericksburg VA
The repoze.bfg Web Application
On 4/8/10 4:36 PM, Marius Gedminas wrote:
from zope.component import getSiteManager
getSiteManager.sethook(get_current_registry)
That seems a bit short-sighted: it would break all tests that rely on
setSite() working.
He said he wanted a global registry, but.. who knows? I stay as far away
On 3/15/10 11:52 AM, Fabio Tranchitella wrote:
* 2010-03-08 18:16, Fabio Tranchitella wrote:
I'll wait till the week-end to release it, so everybody has the opportunity
to have a word on this topic.
I've released zope.component 3.9.3 with the change I discussed on the list
in the last couple
On 3/3/10 2:06 PM, Fabio Tranchitella wrote:
* 2010-03-03 19:59, Chris McDonough wrote:
I think it would be useful to have a discussion about grouping some Zope
bits along functional lines for marketing purposes. This is really
independent of any discussion about the ZTK.
I wonder
On 3/2/10 1:09 PM, Martijn Faassen wrote:
Hi there,
Chris McDonough suggests to ponder further structuring of the ZTK into
separate sub-sets which might allow us to get better mileage regarding
maintenance and release management. He gave the example of the
Bicycle Toolkit
On 3/2/10 2:50 PM, Jim Fulton wrote:
On Tue, Mar 2, 2010 at 2:18 PM, Chris McDonoughchr...@plope.com wrote:
On 3/2/10 1:09 PM, Martijn Faassen wrote:
Hi there,
Chris McDonough suggests to ponder further structuring of the ZTK into
separate sub-sets which might allow us to get better
I nominate Tres Seaver.
- C
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(apologies in advance for the cross-post: we need this to reach the
whole Zope community).
The Zope Foundation board is pleased to announce the regular 2010
general meeting of the foundation
Lennart Regebro wrote:
5. There is also BFG, which doesn't include/build on the ZTK (as the others
do).
Right, it's loosely coupled with the ZCA, but you can throw that out too,
if you like?
Chris has to answer that.
BFG uses some Zope software, like, say, Pylons uses software made by
I nominate Tres Seaver.
- C
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(apologies in advance for the cross-post: we need this to reach the
whole Zope community).
The Zope Foundation board is pleased to announce the regular 2010
general meeting of the foundation
Gah, sorry for the multilist cross-post, this should have gone to the
foundation list only.
- C
Chris McDonough wrote:
I nominate Tres Seaver.
- C
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(apologies in advance for the cross-post: we need this to reach
Everything Tres said I agree with.
I think it's useful for descriptions of Zope-related frameworks to include BFG
and other frameworks that use a small number of Zope technologies. But I think
some distinction needs to be made between the ZTK and some Zope packages.
In particular, I'm
After messing around in the Gimp, and failing utterly, I am sorry, the answer
is no.
- C
Jan Ulrich Hasecke wrote:
Hi,
is there a black on white BFG-logo we can use on zope.de? The white on
black logo from the website is not suitable.
juh
DZUG e.V.
Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I would like to inform you that I intent to retreat from the Zope 2
release manager position soon. I have been serving the Zope community in
this position for almost seven years and now it is time to move on and
Baiju M wrote:
On Mon, Jan 11, 2010 at 10:22 AM, Baiju M mba...@zeomega.com wrote:
Hi All,
There was an adapter registration provides IUserPreferredCharsets.
I can see it has moved to zope.i18n.locales with some others here:
FYI, I just made two new releases:
zope.schema 3.6.1
zope.configuration 3.7.1
These releases provide basic compatibility with Jython.
- C
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
Benji York wrote:
On Sun, Jan 3, 2010 at 6:43 PM, Chris McDonough chr...@plope.com wrote:
Yeah. I haven't thought about this much, so it might be bollocks, but I
think something like this is what I'm after:
.. code-block-setup::
import sys
from somepackage.testing import DummyModule
Strong +1 from me (although my vote is likely not meaningful)
Baiju M wrote:
Hi All,
I am proposing to call Zope 3 - the web frame work
as BlueBream. The main use for name is documentation.
But the package named bluebream will not provide
any part of framework code by itself. All
Lennart Regebro wrote:
On Sun, Jan 3, 2010 at 23:14, Benji York be...@zope.com wrote:
In both of those cases normal doctest blocks seem appropriate.
Not if you don't want the output in the formatting, or if you don't
want the brackets.
Yeah. I haven't thought about this much, so it
Martijn Faassen wrote:
Hi there,
I am interested in creating sphinx-driven documentation for Zope Toolkit
packages. I'd like to maintain the documentation for a package (say,
zope.component) in that package, in a 'doc' directory.
I'm wondering what experiences people have with
I don't think the ZTK as defined by the historical constraints under
discussion here has much attraction for a large number of folks who are
otherwise willing to put effort into maintaining Zope packages.
For these folks, any reduction in number of dependencies and test maintenance
is a net
Benji York wrote:
On Fri, Dec 25, 2009 at 10:31 PM, Chris McDonough chr...@plope.com wrote:
Yeah. I'm a fan of unit tests.
Yep, me too. To be clear, I do want unit tests in the form of a doctest (like
http://svn.zope.org/manuel/trunk/src/manuel/bugs.txt?view=markup). Which may
I added a branch of manuel to the Zope SVN that fixes the codeblock plugin when
you use codeblock roles such as:
.. code-block:: python
:linenos:
Currently it only works without roles, e.g.:
.. code-block:: python
The branch is at
Ugh, that patch is rendered backwards... but you get the idea.
Chris McDonough wrote:
I added a branch of manuel to the Zope SVN that fixes the codeblock plugin
when
you use codeblock roles such as:
.. code-block:: python
:linenos:
Currently it only works without roles, e.g
Benji York wrote:
On Fri, Dec 25, 2009 at 9:37 PM, Chris McDonough chr...@plope.com wrote:
I added a branch of manuel to the Zope SVN that fixes the codeblock plugin
when
you use codeblock roles such as:
Looks good. Add tests and I'll merge and release your branch.
Sorry about
Thomas Lotze wrote:
Chris McDonough wrote:
Thomas Lotze wrote:
Because then, if you use third-party code that uses
zope.interface.Interface and other code (third-party or your own) that
uses the subclassed interfaces, you'll have to deal with both types at
the same time in your client code
Chris McDonough wrote:
Thomas Lotze wrote:
Chris McDonough wrote:
Thomas Lotze wrote:
Because then, if you use third-party code that uses
zope.interface.Interface and other code (third-party or your own) that
uses the subclassed interfaces, you'll have to deal with both types at
the same
Tres Seaver wrote:
I set out to fix these bugs in ZPublisher.WSGIPublisher.WSGIResponse,
and was dismayed to find it an untested hack-up of the original Publish
module, with an untested subclass of HTTPResponse, itself almost
completely test-free. So I went down the rabbit hole, and got
Thomas Lotze wrote:
Chris McDonough wrote:
I'll throw out the obvious...
Why not subclass Interface in zope.component and make the required API
additions there? If it were anybody but us thinking about doing this,
they'd probably just subclass.
Because then, if you use third-party code
1 - 100 of 1687 matches
Mail list logo
