Hi Alex
Betreff: Re: WSGI access log user info howto?
A branch containing this refactoring named
'achapman__username_logging now exists in the zope.app.wsgi
directory. I'll be merging it today and tagging a release if
it appears acceptable.
This looks good to me. Can you add a test
Am 01.04.2009 um 23:44 schrieb Jacob Holm:
Hi Baiju
If this whitespace fix is based on the current style guide, I think
the
guide needs to be fixed. I find the fixed version much less
readable. A
function that takes this many arguments should have an exception to
the
PEP 8 rule of
Michael Howitz wrote:
Am 01.04.2009 um 23:44 schrieb Jacob Holm:
Hi Baiju
If this whitespace fix is based on the current style guide, I think the
guide needs to be fixed. I find the fixed version much less readable. A
function that takes this many arguments should have an exception to the
Hi,
if tests spawn non-daemon threads, then the test runner can get stuck.
The easiest way that I see is to always --exit-with-status and to make
--exist-with-status also call sys.exit() when the tests passed.
Any objections?
Christian
--
Christian Theune · c...@gocept.com
gocept gmbh co.
On Thu, 2009-04-02 at 13:30 +0200, Christian Theune wrote:
Hi,
if tests spawn non-daemon threads, then the test runner can get stuck.
The easiest way that I see is to always --exit-with-status and to make
--exist-with-status also call sys.exit() when the tests passed.
Any objections?
I
On Apr 1, 2009, at 5:44 PM, Jacob Holm wrote:
If this whitespace fix is based on the current style guide, I think
the guide needs to be fixed. I find the fixed version much less
readable. A function that takes this many arguments should have an
exception to the PEP 8 rule of no
On Thu, Apr 2, 2009 at 9:37 AM, Zvezdan Petkovic zvez...@zope.com wrote:
This would be more consistent, is sorted, and ensures easy addition/
removal of each line including the first, and the last line in the
lists.
install_requires=[
'setuptools',
'zope.component',
2009/4/1 Marius Gedminas mar...@gedmin.as:
I now also wonder if adapter()/implementer() would work when called with
classes rather than functions...?
Yes, in 2.6 and 3.0. Not with the current trunk of zope.interfaces,
though, but in the future, sure.
--
Lennart Regebro: Pythonista, Barista,
On Wed, Apr 1, 2009 at 12:25, Chris Rossi ch...@archimedeanco.com wrote:
Additionally, if I was grokking Lennart correctly yesterday,
__metaclass__ is going away, so the current metaclass implementation
is going to need some rejiggering. What was unclear was whether a
single implementation
On Apr 1, 2009, at 5:44 PM, Jacob Holm wrote:
If this whitespace fix is based on the current style guide,
I think so.
I think the
guide needs to be fixed.
Me too, but I don't think it will happen. :(
I find the fixed version much less readable. A
function that takes this many arguments
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
Log message for revision 98787:
zcml now only depends on zope.component meta, not zope.app.component
Changed:
U zope.traversing/trunk/CHANGES.txt
U zope.traversing/trunk/src/zope/traversing/configure.zcml
A
Hey All,
I got bitten by the current zope subversion setup at PyCon so thought
I'd mail the appropriate groups about it. If this has been covered
elsewhere and I've missed anything, please just point me in the right
direction...
So, svn.zope.org causes me pain at the moment:
- it uses the
On Thu, Apr 2, 2009 at 20:31, Chris Withers ch...@simplistix.co.uk wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having access to update the
passwd file and maybe Trac or WebSVN for a nice web interface.
I volunteer to help
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having access to update the
passwd file and maybe Trac or WebSVN for a nice web interface.
I absolutely *hate* using https to access
On Thu, Apr 2, 2009 at 20:39, Jim Fulton j...@zope.com wrote:
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having access to update the
passwd file and maybe Trac or WebSVN for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 20:39 Uhr, Jim Fulton wrote:
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having access to update the
passwd file and
Jim Fulton wrote:
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having access to update the
passwd file and maybe Trac or WebSVN for a nice web interface.
I absolutely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 20:44 Uhr, Andreas Jung wrote:
On 02.04.2009 20:39 Uhr, Jim Fulton wrote:
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people
On Apr 2, 2009, at 2:44 PM, Chris Withers wrote:
This involves storing a key in plane text in my home directory,
which is terrible.
How do you not have the same thing with ssh?
ssh keys are pass-phrase protected and ssh-agent allows me to enter
the pass phrase once in a session.
Jim
--
Jim Fulton wrote:
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having access to update the
passwd file and maybe Trac or WebSVN for a nice web interface.
I absolutely *hate*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
On 02.04.2009 20:44 Uhr, Andreas Jung wrote:
On 02.04.2009 20:39 Uhr, Jim Fulton wrote:
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for
Christian Theune wrote at 2009-4-2 13:30 +0200:
if tests spawn non-daemon threads, then the test runner can get stuck.
The easiest way that I see is to always --exit-with-status and to make
--exist-with-status also call sys.exit() when the tests passed.
I do not understand the implication.
Do
Tres Seaver wrote:
Possibly because I am using SVN 1.6.
Then never means since 2009-03-20. Or else you have never done a
checkout from a password-protected SVN-over-HTTP(S) server.
It's been encrypted on Windows for longer than that...
(svn 1.4...)
Chris
--
Simplistix - Content
Tres Seaver wrote:
Chris Withers wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
I mean an index which supplies the 'simple' PyPI interface, such that we
could tell people to 'easy_install' from it, e.g.:
$ /path/to/bin/easy_install -i http://kgs.zope.org/Zope2/2.1.2
But how
Wichert Akkerman wrote:
Are there other Python projects that have to deal with such a huge
amount of packages and dependencies? I don't know any similar project.
So the solution must come from the Zope world (which does not mean that
we participate in the packaging toolchain development as
Roger Ineichen wrote:
Probably a way to go is to make both concept compatible with
each other. Which probably means we should be able to ignore
versions in packages if a KGS concept get used?
(not sure if this is possible)
NO! This is INSANE!
The version requirements in a package should be
Martijn Faassen wrote:
KGS is two things:
* KGS the software
* KGS the concept
KGS the concept will have a life outside of the Zope world.
I stand by my predication that even the KGS concept will never make it
beyond Zope...
KGS the
concept is very easy to implement; you just make
Chris Withers wrote at 2009-4-2 19:44 +0100:
...
I prefer using password-protected (as opposed to key-protected) https.
What do other people prefer?
I am fine with the ssh access.
True, the initial setup was a bit difficult (the key program
did not like the . in d.maurer -- but forgot to tell
Dieter Maurer wrote:
I would not like to enter my password every time I call svn.
If this can be arranged, I am content.
It can, and with svn 1.6 it's even secure :-)
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
Jacob Holm wrote at 2009-4-2 20:44 +0200:
...
For write access I completely agree. For read-only unauthenticated
access it would be nice to be able to use http(s). It may be possible to
have it all at the same time.
I have been told that there are mirrors of the Zope SVN repository
providing
Remember this:
http://www.perl.com/pub/a/2001/04/01/parrot.htm
Well, that lead to this:
http://www.parrot.org/
One of the reasons I got suckered into replying was that I thought this
might be the result of some stuff a few of us had talked about at the
Zope BOF at PyCon.
I actually think
Dieter Maurer wrote:
I have been told that there are mirrors of the Zope SVN repository
providing read access via http.
Shame none of them is advertised anywhere...
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 21:58 Uhr, Chris Withers wrote:
Dieter Maurer wrote:
I have been told that there are mirrors of the Zope SVN repository
providing read access via http.
Shame none of them is advertised anywhere...
http://svn.zope.de
- -aj
Andrew Milton wrote:
+---[ Chris Withers ]--
| Remember this:
| Seriously, how do people feel about this?
You can do anything you want with your time... who are we to judge? d8)
Well, if there were no complaints I might do just that...
Chris
--
Simplistix -
Martijn Pieters schrieb:
On Thu, Apr 2, 2009 at 20:31, Chris Withers ch...@simplistix.co.uk wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having access to update the
passwd file and maybe Trac or WebSVN for a nice web
On Apr 2, 2009, at 3:57 PM, Chris Withers wrote:
Remember this:
http://www.perl.com/pub/a/2001/04/01/parrot.htm
Well, that lead to this:
http://www.parrot.org/
One of the reasons I got suckered into replying was that I thought
this
might be the result of some stuff a few of us had
Jim Fulton wrote:
What Martijn has announced and is already being worked on extensively.
- Zope A 4.0
What was to be Zope 2.12
- Zope B 4.0
Whatever the next pending release of the Zope 3 appserver stuff was to
be. (Need to keep the Canonical and ZC guys happy afterall ;-) )
On Apr 2, 2009, at 4:17 PM, Chris Withers wrote:
Jim Fulton wrote:
What Martijn has announced and is already being worked on
extensively.
- Zope A 4.0
What was to be Zope 2.12
- Zope B 4.0
Whatever the next pending release of the Zope 3 appserver stuff
was to
be. (Need to keep
Jim Fulton wrote:
We and canonical use the Zope Framework. We don't use an
application. Zope (aka Zope 2) is an extensible application. We (ZC
and Canonical and others) assemble components from the Zope Framework
to build our own applications.
Hmm, maybe I got this wrong, but Gary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 22:17 Uhr, Chris Withers wrote:
I'd *really* like to see the majority of the current www.zope.org simply
eradicated from existence. It's out of date and a source of nothing but
confusion.
Andrew others have been working on this
Andreas Jung wrote:
Andrew others have been working on this issue at the sprint. There is
consensus that www.zope.org must be turned into landing page with some
mission statement and then links to the related subprojects. The current
zope.org site should be moved to old.zope.org (it must
Andrew Milton wrote:
| - mature
| - stable
| - maybe not the best choice for new development.
^ for you
Indeed, but classic doesn't have any bad connotations as far as I'm
concerned, and it'll need to keep living as long as Plone relies on it,
which will be
Andrew Milton wrote:
| Why does it need to keep living even at old.zope.org?
Why do you care if it does?
Because someone needs to look after the (rather large, ancient and
crufty) zope instance in which it lives, and it keeps on tripping up
innocent passers-by.
I don't think many of these
Andrew Milton wrote:
| Indeed, but classic doesn't have any bad connotations as far as I'm
| concerned, and it'll need to keep living as long as Plone relies on it,
| which will be forever...
Plenty of people use it without plone. You might want to crawl out of
the vacuum you live in.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 22:29 Uhr, Chris Withers wrote:
Andreas Jung wrote:
Andrew others have been working on this issue at the sprint. There is
consensus that www.zope.org must be turned into landing page with some
mission statement and then links to the
Andreas Jung wrote:
Because we can't break existing download URL - neither to old Zope
releases
I'd imagine the full set of releases would appear on the respective
parts of classic.zope.org or advanced.zope.org...
nor to old product releases.
I wonder how many of these are actually safe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
Chris Withers wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
I mean an index which supplies the 'simple' PyPI interface, such that we
could tell people to 'easy_install' from it, e.g.:
$
Andreas Jung wrote:
I'd imagine the full set of releases would appear on the respective
parts of classic.zope.org or advanced.zope.org...
*shrug* I don't care if those releases on the new zope2.zope.org
Please not zope2.zope.org, the insane version naming has *got* to stop...
microsite or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 22:45 Uhr, Chris Withers wrote:
Andreas Jung wrote:
I'd imagine the full set of releases would appear on the respective
parts of classic.zope.org or advanced.zope.org...
*shrug* I don't care if those releases on the new
Andreas Jung wrote:
We might discuss this unhurriedly. To sleep and being in vacation mood
in order to discuss this now :-) At least the term 'classic' is a NO-GO
for me.
Why? Would you prefer 'a' or maybe 'old'? ;-)
microsite or somewhere else. The point is that the release should
remain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, this cross-post was inappropriate: it is a matter for general
discussion among Zope committers, which is not a matter for the
Foundation to act on unless / until some consensus for changing the
status quo emerges. This will be my last post to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 22:52 Uhr, Chris Withers wrote:
Andreas Jung wrote:
We might discuss this unhurriedly. To sleep and being in vacation mood
in order to discuss this now :-) At least the term 'classic' is a NO-GO
for me.
Why? Would you prefer 'a'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 2, 2009, at 22:53 , Tres Seaver wrote:
+1 to making svn-over-http read-only checkouts work.
This is now working. The repository can be reached under...
http://svn.zope.org/repos/main/
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG
On Thu, 2009-04-02 at 20:43 +0200, Martijn Pieters wrote:
On Thu, Apr 2, 2009 at 20:39, Jim Fulton j...@zope.com wrote:
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
For me, the ideal would be simply https for everything and using http
basic auth for access with more people having
On Wed, Apr 01, 2009 at 11:44:03PM +0200, Jacob Holm wrote:
If this whitespace fix is based on the current style guide, I think the
guide needs to be fixed. I find the fixed version much less readable. A
function that takes this many arguments should have an exception to the
PEP 8 rule of
On Thu, Apr 02, 2009 at 01:30:38PM +0200, Christian Theune wrote:
if tests spawn non-daemon threads, then the test runner can get stuck.
The easiest way that I see is to always --exit-with-status and to make
--exist-with-status also call sys.exit() when the tests passed.
Any objections?
On Thu, Apr 02, 2009 at 07:31:00PM +0100, Chris Withers wrote:
So, svn.zope.org causes me pain at the moment:
- it uses the bizarre svn or svn+ssh protocols, which I find annoying
(ports blocked on routers, can't check with a browser, etc)
+10 for continuing to support svn+ssh, it's the
On Thu, Apr 02, 2009 at 01:08:51PM -0400, Tres Seaver wrote:
Gary Poster wrote:
Log message for revision 98787:
zcml now only depends on zope.component meta, not zope.app.component
Changed:
U zope.traversing/trunk/CHANGES.txt
U
On Apr 2, 2009, at 1:31 PM, Chris Withers wrote:
Hey All,
...
The other option would be to follow Python and move to Mercurial, but
that has the same problems for me as with Bzr (no decent gui tools,
less
mature, etc) although it's a toolset I'll have to learn at some point
anyway...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
I'd like to report back on the progress that Bzr/Launchpad has made
addressing concerns we heard since I last brought up Canonical's offer
to host the code and contribute commercial support for the transition.
When I do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2009 22:53 Uhr, Tres Seaver wrote:
*This* part needs some fixing, largely because Jim's role their is an
artifact of ZC's role, now lapsed, as custodians. At a minimum, there
should be a group (I suggest the zope-web regulars) who can
Hi Malthe
I just improved coverage in z3c.form and found a bug in
z3c.pt.
Can you run the group.txt tests in z3c.form and confirm
the issue. A div tag get skipped after some nested repeat
tags. (line 898, in group.txt)
Is this a known issue?
Can you fix this or give me some hints which let me
62 matches
Mail list logo
