tions off, for use by other
code that is still in need of debugging.
I've heard that this works very well, and in Python 3000 (when we have
optional static typing) I would love to add this to Python. If it's
not feature bloat.
--Guido v
making sure that you get all the
> needed data into the new index...)
What was the use case for switching lexicons in the first place? I
bet it was just someone idly playing around and noticing that it
didn't work right...
--Guido van Rossum (home page: http://www.python.org/~guido/)
__
that the pipeline
options need to be selected when you create a ZCTextIndex -- this is
actually simpler because it's now one-stop shopping (except for the
need to still create a ZCatalog).
--Guido van Rossum (home page: http://www.python.org/~guido/)
_
27;ll do this.)
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.o
t
one Zope Corp customer).
Here's a copy of my original announement:
>Subject: ZEO cache analysis tools prerelease
>From: Guido van Rossum <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Date: Tue, 10 Sep 2002 17:02:41 -0400
* Do you want to know if your ZEO client cache is con
best idea; on Windows, localhost would prevent
access from outside the machine, and Windows boxes typically have only
one user, so I'm not concerned about internal attackers.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Z
> Guido van Rossum wrote:
> > A while ago I announced a new ZEO cache instrumentation feature, and
> > asked if anyone was interested in enabling this instrumentation in
> > their site. I got exactly zero responses... :-(
>
> Hmmm... people might have done it an
Controller that might take a while to catch up.
I'm not planning to change the default startup configuration -- we're
just adding the ZEO code so that you don't have to download and
install it separately.
ZEO has been added to the trunk now -- enjoy!
--Guido van Rossum (home page
erhead really that much?)...
I'm not sure that such a drastic change can be done without breaking
expectations set by previous Zope releases. But I'll let the Powers
That Be decide on this -- I'm not touching the default configuration.
--Guido van Rossum (home page: http://www.
about the ones that
particularly bug you -- with patch if you've got a suggestion.
We'll get there still.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/z
has contained a lot of places where "except:" was
used when the author knew exactly which exceptions he was expecting.
To make it worse when this is sometimes done for a large stretch of
code, even though there are only a few specific spots where the
exception is expected.
--Guido van
me it.
I'm skeptical about this one. Can you explain the use case?
You can probably fake this to a large extent by using "except
Exception:" instead of "except:" everywhere; then you can raise an
exception that does not inherit from Exception.
--
Have you tried clearing your cache after reverting the ClientCache.py
change?
Are you sure you didn't use the ZEO2 ClientCache.py with a ZEO1
installation or vice versa?
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zop
ssage,
and exit. (I took the criterion, but not the response from init(8).)
Are there any concerns about checking this in? This would go into
Zope 2.7 and ZODB 3.1, and could possibly be backported to 2.6 and
2.5.
--Guido van Rossum (home page: http://www.python.org/~
0-05T04:24:12 ERROR(200) zdaemon zdaemon: Sat Oct 5 04:24:12 2002:
Aiieee! Process 2915 terminated normally, exit status: 1
--
while it could look like this:
--
2002-10-05T04:23:31 INFO(0) zdaemon Started subprocess: pid 2915
--
2002-10-05T04:24:12 ERROR(200) zdaemon Process 2915 terminate
emon is the default at all), but for
a production site something different might be in order.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No
red TCP ports.
>
> IMO there are better solutions to the problems to which low-numbered
> ports are a common solution. Zope/ZSS never *needs* a low numbered
> port, and zope should never be started as root.
Correct.
> (I have cc'ed zope-dev. I suggest we continue there, rathe
t on to the server process. Ive only just discovered
> that:
>
> a. The signal forwarding doesnt seem to work for me
>
> b. The default stop script doesnt use this pid.
How typical.
One problem here, as always, is that the conventions are undocumented,
or at least not docume
Chris M has been looking at zope logging
> recently - Im not sure if that work could be applied to ZEO too.
I'm not sure how daemon support and better logging are tied together?
I was thinking of letting the daemon manager use zLOG just like
everybody else.
--Guido van Rossum
OG -- can I get rid of it too?
The SignalHandler.py class is not used by zdaemon itself; perhaps it
can be moved into the Signals package?
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http:/
Index offers.
It's easy to add your own splitter by writing a few lines of Python
code. RTSL.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listin
ut of the box. and that's what the patch for...
I must've missed the start of this thread (I only just signed up for
this list). I didn't see any patch -- I thought it was just a gripe
about ZCTextIndex. Of course patches are welcome -- where can I find
this particular patch?
--Guido va
> I think all these things are reasonable things to do...
>
> Guido van Rossum wrote:
> > The zdaemon package contains a bunch of dead wood, or "decoys", as Jim
> > would call it, that I'd like to remove. AFAICT, Heartbeat.py is not
> > used anywhere.
sn't with the thing that is advertised on the Add
> form as the replacement, and that just isn't cool.
Indeed.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.z
> > > The SignalHandler.py class is not used by zdaemon itself; perhaps it
> > > can be moved into the Signals package?
>
> Will do.
Done.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist -
etter
> > configuration and management of ZEO and ZODB.
>
> Is 3.2 work happing on the trunk or a branch?
I presume it's going on the trunk. Is there a problem with that?
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
e to set sys.hexversion to 0x0202 (or to 0 if
you're not sure which Python version you're using) before importing
sre for the first time.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAI
> On Tue, Nov 19, 2002 at 01:54:56PM -0500, Guido van Rossum wrote:
> >
> > > Since I don't actually use Zope 2.6, does anyone have an idea on
> > > where the problem may come from ?
> >
> > You're using restricted mode (the rexec module) and t
ot the case that it's wasting RAM disk space
by writing cached data to disk that's also in memory.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listi
. Any assistance would
> be great!
Try this:
http://cvs.zope.org/ZODB3/ZEO/README.txt?rev=1.4&content-type=text/vnd.viewcvs-markup
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://li
w to find that out. Any assistance would
> > be great!
>
> Try this:
>
> http://cvs.zope.org/ZODB3/ZEO/README.txt?rev=1.4&content-type=text/vnd.viewcvs-markup
Simpler would be to check your log file for "cache flip" messages. If
you get these more than a few times
27;s your code for
X?" -- there's so much good stuff in your branch that I don't know
where to begin, especially not with the Zope part (in ZODB, I know my
way around better).
--Guido van Rossum (home page: http://www.python.org/~guido/)
__
It could be a semi-bug in the
platform malloc where the allocation and deallocation pattern of your
test happens to cause worst-case fragmentation. Using Python code
probably changes the allocation pattern enough to avoid the
fragmentation.
--Guido van Rossum (home page: http://www.python.org/~gu
feature), ZConfig uses a more
readable format. It's documented in the ZConfig CVS tree.
> ZRS? This isn't the long-discussed replicated storage is it?
Yes, http://www.zope.com/Products/ZopeProducts/ZRS
--Guido van Rossum (home page: http://www.python.org/~guido/)
a good idea. With Zope,
bleeding edge developers have access to CVS, so there's no need for
such "releases".
A bugfix release for Zope 2.6.0, named Zope 2.6.1, was planned for
this week. But yesterday, three new bugs in 2.6.0 were reported, and
we'd like to fix those too. With
up as often as a bug is discovered
> and fixed...
That means we either waste a lot more time doing releases, or the
releases become a lot more shoddy, hardly more than a snapshot from
CVS. Neither sounds attractive, sorry.
--Guido van Rossum (home page: ht
ptions, and I think
an unqualified except: clause is okay here (though it needs a
comment).
Also note that the unpatched code has an unqualified except: already,
so you can't really blame Dmitry.
--Guido van Rossum (home page: http://www.python.org/~guido/)
_
et an OverflowError, but that can only happen
when the input is a Python long or float -- int("999")
raises ValueError, as does int("xxx").
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-
lueError *only*
On converting a Unicode string to an int:
ValueError
UnicodeError (or UnicodeEncodeError, which is a subclass of it)
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists
Sorry, cc'ed the wrong list. :-(
--- Forwarded Message
Date:Wed, 11 Dec 2002 10:29:12 -0500
From:Guido van Rossum <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] (Jeremy Hylton)
cc: [EMAIL PROTECTED]
Subject: Re: [ZODB-Dev] Fwd: [Zope3-dev] directory hierarchy propos
value = expression_to_compute_value
>try:
>i = int(value)
>except ValueError:
># take corrective action
>
> rather than:
>
>try:
>i = int(expression_to_compute_value)
>except: # Note: calling 'int()' can raise just a
rror is a subclass of ValueError. So
catching ValueError from int(str_or_unicode) is the way to go. Who's
writing that Zope 3 style guide again?
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAI
ypical use case. You could
implement a file size limit, or increase the cache size to be more
than twice the largest expected dowload (the cache is implemented as
two files, each of which is limited to half the nominal cache size).
--Guido van Rossum (home page: h
pe is v2.5.1)
>
> [root@prefect Zope-2.5.1-linux2-x86-dev]# cd lib/python
> [root@prefect python]# python
> Python 1.5.2 (#1, Apr 3 2002, 18:16:26) [GCC 2.96 2731 (Red Hat Linux
Um, Zope 2.5.1 requires Python 2.1.3 or later. You're using Python
1.5.2 here. That's p
rk arounds that make the whole system harder to
> understand.
+1.
Remember the XP dogma: refactor mercilessly.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/lis
Indeed -- the nightly unit tests also pointed this out.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encod
PyCon in DC. If there's enough
demand (and/or if people will pay for the space) we can get space at
the PyCon venue the two or three days before the conference proper for
an extended sprint.
--Guido van Rossum (home page: http://www.python.org/~guido/)
__
2.7 shouldn't require Python
2.1.3 rather than 2.2.2. The original motivation for requiring 2.2.x
was to allow easy backporting of Zope 3 components, and that is no
longer a goal. I've asked Brian to review the version decision in
this light.
--Guido
> Without python 2.2 zope will continue to harbor remotely exploitable
> zlib-based memory exhaustion attacks. FWIW
Can you explain? Where does Zope even use zlib?
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev ma
> On Saturday 11 January 2003 4:06 pm, Jamie Heilman wrote:
> > Guido van Rossum wrote:
> > > > Without python 2.2 zope will continue to harbor remotely exploitable
> > > > zlib-based memory exhaustion attacks. FWIW
>
> There are workarounds that work in 2
it. I think 2.7 would
be in the same boat.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists
1.x and 2.2.x. It would be nice not to have to do this when
> developing 2.7 only code. I realize that this would be necessary
> when backporting things to 2.6.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist -
this is moot. In the mean time I ask not to use
Python 2.2 features like bool gratuitously.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** N
plain annoying. On Unix
> you can always tail the logfile for the same effect.
I do not understand this remark. Your patch *prevents* the daemon
from detaching. So you find your own patch annoying?
--Guido van Rossum (home page: http://www.
failures=1)
==
OVERALL FAILED (total failures=1)
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related list
g mode for ZEO *only* determines
whether the ZEO server goes into daemon mode or not. There may be a
Zope debug mode, but it's not related (even if it uses the same
envariable).
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zo
> On January 21, Guido van Rossum wrote:
> > There may be a Zope debug mode, but it's not related (even if it
> > uses the same envariable).
>
> I'm sorry, I'm talking about Zope's debug mode.
Eh? This started with your suggesting a change to ZEO/start.p
're right. :-(
I know that file from the context of ZODB. But it is also used by
Zope. I'm sorry for the confusion.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.
, Zope 2.7 will use zdrun.py
from the ZODB 3.2 CVS for process management.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross pos
INAL; RELEASE
> ANOTHER BETA!!
If only it were that easy. Everybody wants "no new features" except
for the one feature they desperately want to have without upgrading to
the next feature release. :-(
--Guido van Rossum (home page: http://www.python.org/~guido/)
> Guido van Rossum wrote:
> >
> > If only it were that easy. Everybody wants "no new features" except
> > for the one feature they desperately want to have without upgrading to
> > the next feature release. :-(
>
> Still, we're back to the
[me]
> AFAIK most people use Apache's mod_redirect to a Zope HTTP server
> running at (e.g.) port 8000. No additional software needed.
I meant mod_proxy of course.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-D
at (e.g.) port 8000. No additional software needed.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Rel
cify the host to bind to.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope
upgrade to Zope 2.6.1 as well?
If not, what exactly is in the logs? Note that you need to have the
new ZEO in the Python path both on the client side and on the server
side.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev
arately usable, just like we do for ZODB?
Just how much did you have to change to divorce ZPT from Zope?
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-de
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
ckers should be used for real
coding issues.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related l
IMO TALES should solve this for itself by introducing an if/then/else
expression form rather than depending on Python. If you can have a
"not:.." expression, surely you can have an "if:..:then:..:else:.."
expression.
--Guido van Rossum (home page: http://www.python.o
up this week).
The no-detach choice is already separate -- this is now an option to
the separate zopectl program.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailma
#x27;ve won. Some of the breaks have already
> been made, like the separation of the storage from its front-end.
> Thats good, we need more action along those lines.
You're barking up the wrong tree. Zope 2 won't change. Zope 3 is
still in a state of flux, and that's where
> On Tue, 2003-03-11 at 15:22, Guido van Rossum wrote:
> >
> > That's why we're including the correct versions of ZODB and ZEO in
> > Zope itself. That's already the case in Zope 2.6.
>
> Zope 2.6 doesn't yet include ZEO, at least I don't th
ts own install and config stuff,
which is very similar to that for Zope, but ZEO is not installed as
part of the main Zope install.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.
ing to do would be to package up a ZEO server
> installer separate from Zope 2.7 with a similar kind of buildout,
> support files, and configuration file. At least that's been my idea so
> far.
Not needed; it's all there (though far simpler in approach than the
Zope installer)
nt to run a ZEO server
> to just run mkzeoinst from the software home resulting from Zope's "make
> install" and to edit zope.conf to use a ClientStorage?
That should work, yes, as long as mkzeoinst.py, zdctl.py, zdrun.py and
runzeo.py are all on $PATH at that point.
--Guid
iguration data as it uses for the associated Zope instance, so they
> both know to use 'var/zeo.soc' to connect.
zdrun takes care of auto-restart.
Sharing config data may be a little trickier; Fred and/or Chris should
know more about that.
--Guido van R
> I thought you had to install ZEO on top/inside of an existing Zope
> installation. Will this be different in Zope 2.7?
Yes, ZEO will be an integral part of Zope then.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zo
don't know. What's confusing for you? The new approach is that:
Zope includes ZODB includes ZODB
What's confusing about that?
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTE
et ZEO is a bit of a pain. Also, ZEO is packaged differently in
> the stand alone ZODB than it used to be in on it's own.
That's why we're including the correct versions of ZODB and ZEO in
Zope itself. That's already the case in Zope 2.6.
--Guido van Ross
has its own schema and tools, also based on
ZConfig and the new zdaemon; you can check these out in the ZODB 3.2
alpha release.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org
a
showstopper for you. If you find problems, please report them here so
they can be fixed in Zope 2.7!
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/
nals, not for discussing how to use Zope and its API.
Maybe the bottom message should be clearer on the purpose? "No cross
posts" doesn't really help one decide which list to use.
"zope-dev" == "development using zope" sounds p
B 4 (== Zope 3). If it were up to me,
they would have been gone, with a big helping of YAGNI!
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zop
> Perhaps Jeremy could run through his reasons for wanting them to
> stay around again?
That's not necessary. They could stay in ZODB (certainly cutting them
out of ZODB3 now would be more work than leaving them in) but be
disabled in ZMI.
--Guido van Rossum (home page: http://www
>about Zope's support for Python Labs and branding.)
I'm not sure what you mean by that final remark, but I also like to
install scripts with their .py extension. Some at PL disagree though.
--Guido van Rossum (home page: http://www.python.org/~guido/)
__
The deadline for submissions to PyCon DC 2003 appears to have been too tight
for many authors. While some promised submissions have arrived, several have
not even though the original deadline of 15 December has passed.
Rather than exclude promising papers the organizing committee has decided to
ex
86 matches
Mail list logo
