>>> Shane Hathaway wrote
> I looked some more at ZClasses and such today, hoping to solve the
> problem with mounted databases. Guess what! It turned out to be a
> simple matter.
Excellent! I've added support in CVS, and I'll do a new release this
evening.
> The latest addition to Mount.py pro
.software.testing
>
> ___
> Zope-Dev maillist - [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-announce
&
___
> Zope-Dev maillist - [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailm
ver happen. (Waaa).
Well, it has happened, and I'd like it to go away. Any ideas what causes
this?
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTEC
Ok, I got a quick workaround by making a new Product, and creating the
permissions it needed inside there.
I _suspect_ the problem was caused by nested ZClasses.
Uuuugly.
Anthony
>>> Anthony Baxter wrote
>
> I'm trying to export/import a ZClass based product from one
>>> KevinL wrote
>
> Please, please, please, do _not_ use IP numbers to verify it's the same
> connection. You guys don't have the problem in .us, but out here at the
> fringes (.au, and presumably .uk and similar), proxy server use is rampant -
> and leaning on IP breaks, because proxy's sha
he tree tag (btw, in case no-one's repeated it recently, the tree tag
is Pure Evil From Planet Ten, and must be destroyed :)
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-De
PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-announce
> http://lists.zope.org/mailman/listinfo/zope )
>
--
Anthony Baxter <[EMAIL PROT
>>> [EMAIL PROTECTED] wrote
> I've run into several greedy except: clauses now, and have submitted
> patches to make them a little less greedy. Out of curiosity, I searched the
> Zope source for "unfiltered" except: clauses...
> % grep -rl "except:$" . |wc -l
> 102
> ... erk
Erk and a lot. This
> > Is it the sort of thing where it's just work putting a list of all of
> > them (line numbers, &c) up on a web page, maybe crosslinked into cvsweb?
> > Then people can go and pick them off, one at a time.
ok dokey - so, is DC still running a source view web system? If so,
you could easily eno
ooo. Richard didn't do it right - there's actually over _600_ bareword
except: clauses in the current zope-2_3-branch
A quick breakdown of some of the biggies:
71 in OFS/
61 in ZODB/
56 in ZServer/
53 in ZGadflyDA
50 or so in what seems to be test scripts or modules (probably ok)
42 in ZPublishe
Ok, my last for tonight - I put the output of my horrible script at
http://www.zope.org/Members/anthony/BarewordExcepts
I'll work over it a bit probably early next week - an obviousish next
step is to make it note when the body of the except: contains a 'raise'
statement.
Anthony
ix.
(hm, in the case where a bare except _is_ genuinely what's wanted,
could we put a comment in the source to make it easier to strip
them out).
Anthony, working towards an "except:" free-world :)
>>> Jeremy Hylton wrote
> >>>>> "AB" == Anthony
Any known gotchas with running ZEO server and ZEO client on boxes of
different endianness? e.g. the server running on sun solaris/sparc,
while the clients are on x86 linux boxes.
I'd expect it to be fine, but am feeling paranoid...
ta,
Anthony.
___
Z
As far as I can see, ZEO clients don't write a pid to Z2.pid until
after they've successfully connected to a storage. Is there a reason
for this?
Ta,
Anthony
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**
hing for the core
package? Ideological reasons? How does releasing under the GPL make
the world a better place?
Anthony, who's seen too much of the GPLd-for-GPLs-sake.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
he ZPL is GPL compatible, they can make their components GPLd.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/l
Tcl or (god help us all) Javascript/ECCCHMAScript.
I can't see cisco agreeing to opensource IOS so that they can embed a
decent language in it.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
_
f->ring;
home->prev = &self->ring;
}
So it seems that the ring's getting corrupted in some way. Any tips on
tracking this down? I'm thinking of a simple function that just zips
around the ring checking that it's sane in both directions...
(yes, I've co
More information: I don't see the failure with a fresh Data.fs. The
Data.fs in question is my 2.5 one. I'm running the current HEAD of
Zope-2_6-branch. I packed the Data.fs, the same result.
I've added a simple function to 2.6's cPersistence.c:
static void
ringcheck(CPersistentRing *start)
{
>>> Toby Dickenson wrote
> On Friday 25 July 2003 08:30, Anthony Baxter wrote:
> > More information: I don't see the failure with a fresh Data.fs. The
> > Data.fs in question is my 2.5 one.
>
> Do you have any custom persistent extension classes stored in that
or
cosmic rays.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(R
>>> "Tim Peters" wrote
> Jeremy and I saw cases of ring corruption while putting together the
> experimental ZODB 3.3, but they were 100% reproducible on all platforms, and
> turned out to have clear causes (some of the C objects we backported from
> ZODB4 were getting ghostified by the ZODB4 code
So I see ZEO clients here falling over all over the place under current
2.6 with:
2003-07-30T07:01:04 ERROR(200) ZEO uncaptured python exception,
closing channel
(exceptions.AttributeError:keys
[/export/01/zope/dev_ekit/ZServer/medusa/asyncore.py|poll|94]
[/export/01/zope/dev_ekit/ZServer/me
>>> Anthony Baxter wrote
> So I see ZEO clients here falling over all over the place under current
> 2.6 with:
>
> 2003-07-30T07:01:04 ERROR(200) ZEO uncaptured python exception,
> closing channel
>
> (exceptions.AttributeError:keys
> [/export/01/zope/de
the one that's in 2.6.2. :-/
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts
>>> Anthony Baxter wrote
> Updating it by hand to ZEO2 hasn't made all good and happy, though -
> the ZEO/start.py includes
> import ThreadedAsync.LoopCallback
> at the top of the file, but the sys.path magic that makes this
> available is inside the main() functio
I remember that 2.6 had issues with packing, but I was under the
impression that they'd been fixed...
However, attempting to pack a Data.fs in 2.6-current-cvs fails
for me:
File "/export/01/zope/dev_csr_code/lib/python/ZODB/DB.py", line 526, in pack
try: self._storage.pack(t,referencesf)
Woohoo! Fixed. I created an empty file, then used copyTransactionsFrom
to copy all transactions across. This patched the backpointers. fsrecover.py
should probably get some smarts to do something like this as well, but I've
spent far too long on this problem already... :-/
from ZODB import FileS
>>> "Jeremy Hylton" wrote
> I don't recall that any of the pack bugs that we fixed caused this sort of
> error. My first guess would be that the file is a bit damaged, perhaps in a
> way that the old pack did not check.
> Can you run fsdump.py and see if that output sheds any light. It will give
> /zope/Zope-2.6.2b5-src/lib/Components/ExtensionClass/src/ExtensionClass.h:94:20:
> Python.h: No such file or directory
It can't find Python.h - it's looking in /usr/local/include/python2.1
for it - is the file there? Is it readable by the user that the build
is running under?
appen a lot faster.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
Go to the Find tab in the ZMI, select "All types", containing ""
Error type: TypeError
Error value: expected a character buffer object
Traceback (innermost last):
Module ZPublisher.Publish, line 49, in publish
Module ZPublisher.mapply, line 32, in mapply
Module ZPublisher.Publish, lin
them - is this
something that could/should be included with Zope?
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/lis
d no longer be needed (logging,
> csv, gettext).
Don't forget you also get the C version of datetime.
> I also don't know that we should consider 2.3.1 "acceptable" for any
> version of Zope.
Meh. 2.3.1 gets a bad rap. Aside from the fsync problem, there's nothing
ll
possible to check against, say, a 2.7 beta.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope
>>> "alan milligan" wrote
> Guys,
>
> I've just run into a problem and wondered if there was an elegant
> resolution.
>
> My BastionBanking package contains:
>
> currency.py - pure python
> Currency.py - Zope derivation
The "typical" approach in Python is to have, e.g. Tkinter, an
t case that states something like
"No config file, use Zope.configure('configfile')"?
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROT
ic thing, not something that requires manual
intervention.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/list
Zope, that are at fault. Of
course, if it's memory corruption, this could be tricky to figure out...
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
ht
it's fine under load.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
I got completely fed up with the Zope 'Find' stuff not being about to
traverse through Products/Foo/FooProduct, where FooProduct is a ZClass.
The following patch adds this support to the FindSupport.ZopeFind method
through the simple fix of saying "if it's a ZClass, keep looking in
ob.propertyshe
>>> "Morten W. Petersen" wrote
> Will a ZPL-ish license [1] be accepted (declared, ref. paragraph
> 4 of the Zope Contributor Agreement) by the Zope Corporation?
> [1] http://www.thingamy.org/tpl
Um, this license would seem to have the "obnoxious advertising clause"
problem - it requires you to
I've got Zope code and installation pretty heavily automated here,
but one thing that takes a while is that after a cvs update, I have
to do a complete wo_pcgi on each box to make sure everything's up to
date. This forces everything to be rebuilt. Is there anything that
could be done to make it o
think of somewhere inside Zope that
generates this sort of structure? "c_o_s" is a string we use in
our code as a property, a database column, and a REQUEST variable.
As far as we can tell, it's not something being generated by
our code...
Thanks,
Anthony
--
Anthony Baxter <[EM
>>> Chris McDonough wrote
> I'd be tempted to suspect the BTrees module setstate code.
Yeah? This is something that you'd expect to see with it?
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never t
_
> Zope-Dev maillist - [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-announce
> http://lists.zope.org/mailman/listinfo/zope )
>
--
Anthony B
's correct, unfortunately...)
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or H
Someone's busted the help system recently. On a system running the
current Zope-2_4-branch, I get:
For the URL http://ekit-host.ekorp.com:8880/HelpSys/menu
No error message.
Error type: TypeError
Error value: Catalog addIndex now requires the index type to
be resolved prior to a
ch lately) it
can be fixed before the next 2.4 release.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
Running current Zope 2.4 CVS under python 2.1 built --without-cycle-gc,
I'm seeing an absolutely _enormous_ amount of leaked objects in
RestrictedPython. This is on one of our ZEO clients, after 45 minutes
of runtime. The deltas are after 5 minutes.
RestrictedPython.compiler.transformer.Transfor
>>> Jeremy Hylton wrote
> Do you have any more idea about what shutting the garbage collector
> off achieves? In practice, the garbage collector's most common effect
> is to turn latent bugs into manifest bugs; a bug has trashed part of
> memory and the garbage collector just happens to find it f
>>> Leonardo Rochael Almeida wrote
> >From my mile-high look at the issues, it seems like the cycle-gc asks
> for an object where to look for for it's references (at least thats what
> the tp_traverse function looks like it does). So, if your tp_traverse
> sends the gc somewhere it shouldn't go (o
cycles, and we found we couldn't run a zeo client on a nogc python for
more than about an hour.
ah - here's the message I sent:
Date:Wed, 17 Oct 2001 18:10:27 +1000
To: [EMAIL PROTECTED]
From:Anthony Baxter <[EMAIL PROTECTED]>
Subject: RestrictedPython under no-GC 2.
readme note or similar saying "if
you're using pythonscripts, don't bother without cyclic GC".
For me, I run the ZEO server without GC (because that stops the stomped
stack bug killing the ZEO server), and the ZEO clients with GC (and just
wear the restarts.
--
Anthony Baxter
>>> "Matthew T. Kromer" wrote
> Anthony Baxter is anticipating a Python 2.1.2 beta real soon now (probably
> this weekend) so I am going to try to get that into Zope 2.5's binary
> releases, although we may put out a Zope 2.5 beta 3 first. This will
> inc
wanted to do this, once the release candidate is out -
I don't have access to a massive number of platforms, so I'd like to know if
I've accidentally broken anything. :)
Watch this space...
--
Anthony Baxter <[EMAIL PROTEC
making
it part of the preinstalled set of Products, I'd _strongly_ urge that
the documentation for it be updated.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist -
./Modules/gcmodule.c:170
> #1 0x0806ff74 in collect (young=0x80b228c, old=0x80b2298) at
> ./Modules/gcmodule.c:382
> #2 0x080701c2 in collect_generations () at
> ./Modules/gcmodule.c:479
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late
RestrictedCompiler fix?
As far as I am aware, Zope 2.4 includes it's own version of the
Compiler code, and the current release of 2.4 still has the stacksize
bug.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
_
em is only in
> the GC module of Python because zope is running without any crashes when
> I disable GC.
The bug's still there, it's just that the corrupted data is hit much
more frequently when GC is on.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]&
> object switches threads, it can get unhappy (I think something in MySQL
> may have thread-local state).
In that case, how about cutting a version which is 2.4.3 + the compiler
fixes? Crashes are bad, and it would be very nice to Make Them Go Away. :)
Anthony
--
Anthony Baxter <[EMA
>>> Behrens Matt - Grand Rapids wrote
> Anthony Baxter wrote:
>
> > In that case, how about cutting a version which is 2.4.3 + the compiler
> > fixes? Crashes are bad, and it would be very nice to Make Them Go Away. :)
>
> You already have that. Check out
>>> "Olivier Deckmyn" wrote
> assertion "STACK_LEVEL() <= f->f_stacksize" failed: file "Python/ceval.c",
> line 687
This is a new assertion, put in to catch the case where the RestrictedCompiler
code used by PythonScripts incorrectly calculates stack size.
> After some hours of researches, I hav
>>> Richard Jones wrote
> I've just announced our Call Profiler product on zope.org and the zope
> announce list (waiting for people in different timezones to authorise them :)
> ( http://www.zope.org/Members/richard/CallProfiler/ for the impatient)
>From my point of view, this is a critical
(apologies for formatting oddness - at conference, so don't have access
to normal mailer. _hopefully_ this will be in plain text...)
Andy Sydelko wrote:
>Has anyone actually used multiple FastCgiExternalServer
>directives within apache, each pointing to a separate ZEO
>client, to load balance?
cult task - I can
give a sample bit of source if it would help...)
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never to late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/
up with zero slowdown when not profiling.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never to late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No
s. don't forget Anthony, our first reaction when we both thought of this
> approach was *shudder* :)
Sure, but after tinkering a bit, and compared to the original hack that
I did, this is sooo much cleaner. The amount of work required to
instrument a new object is close to zero.
Anthony
hony
[1]
Seagoon: Here! Have a gorilla.
Eccles: Oh! Thanks.
Grams: [Two gorillas fighting, or if you can't get that, lions.]
Eccles: Oww! Oww! Ooh! Oww! Hey! These gorillas are strong. Here!
Have one of my monkeys -- they're milder.
-- http://www.residents.com/Goons/napoleo
>>> Nicola Larosa wrote
> you should read the Stability Howto:
>
> http://www.zope.org/Members/matt/StabilityHOWTO
This docco doesn't clearly state that you MUST recompile your
pythonscripts when upgrading to 2.4.4+ (when do we see a real
2.4.4, anyway?)
Anth
e GC is the thing that falls over and
breaks.
I think I've mentioned it before, but looking at the object _before_
the corrupted one in memory might be a useful thing to try...
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's n
? The host running the ZEO server? The host
running the ZEO client? What about those of us who run multiple ZEO clients
on the same machine (multi-cpu, test instances, whatever)...
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never to late to have a happy childhood.
__
>>> seb bacon wrote
> But we come back to the point that you may be logged into one of (say) 3
> app servers (ZEO clients) all serving the same domain, no?
and on the same box ... :)
Anthony
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zop
>>> "Adrian Hungate" wrote
> moved to a different thread or earlier, before the fork, so that we could
> simply kill senile threads without killing the entire shooting match?
unfortunately apache does this with seperate processes, not threads.
memory corruption and leaks aren't solved by offing
>>> Casey Duncan wrote
> I don't think this is a big enough change to warrant a real proposal, so
> I'll shoot this out here:
>
> Does anyone see a problem with changing the default generated
> constructor method for ZClasses to a python script in Zope 2.6?
+1.
There's always some funniness
k would be
my guess for a release. At the moment it's looking like a source release, with
RPMs and and ActiveState windows packages. I don't think there'll be a PythonLabs
windows binary release, and there wasn't a 2.1.2 Mac binary release, either...
Anthony
--
Anthony Baxter
nd of the next killer mongrel bug warming up, just offstage?
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listi
Python 2.1.3 is out. See http://www.python.org/2.1.3/
This release _should_ now make Zope happy - it has the recent
bugfix for the GC/Trashcan interaction ugliness.
I'd recommend anyone running Zope 2.4 or 2.5 to upgrade to this
version, in particular if you use PythonScripts.
Anthony
_
make it _very_ obvious when it's being used. Storing stuff in
a session is often one of the critical bits of a web request, so it's
important to me that it be clear and easy to see this.
Anthony
[*] I assume the standard Zope session stuff has adopted the SESSION
convention now? it wasn&#
risW-ly yrs,
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encodi
> Chris - stay in the stone age, I hear they have fire there ;-)
mmm. fre pretty.
"Page Templates burn, don't dey. Be a shame if somefing was to happen
to your nice shiny website".
Anthony, who might have been spending too long in the bad places of SQL.
n a randomly
numbered port. I'd say it's almost _certainly_ a firewall issue.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org
luestack) <= f->f_stacksize' failed.
You should be running 2.4.4 or 2.5.1. This is a known bug in 2.4.3.
(It only shows up under python 2.1.3 or later - earlier versions of
python silently corrupt memory).
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
I
in the python bugtracker :)
If there was a Zope FAQ, I'd say this one'd get an entry.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
ht
I haven't yet finished of the CallProfiler bits, but it's a long weekend
here, and I plan to attack and finish it over this weekend. I've had more
of a go at the refresh problem, and I think I'll just make sure there's no
refresh.txt for now :(
Anthony
--
Anthony Bax
to get rid of the warnings?
Thanks,
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cr
>>> Leonardo Rochael Almeida wrote
> It is possible to run 2.6 under Python 2.2, but it's unsupported
Note that you'll need 2.2.2. 2.2 and 2.2.1 have bugs that Zope triggers.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never t
>>> Dieter Maurer wrote
> I am almost sure, you no longer need it.
> At least, we use Python 2.1.3 compiled without this option
> and do not see problems (attributable "malloc").
The (known) bugs that pymalloc (and cycle-gc) triggered are
fixed in 2.1.3.
Anthony
--
yes" or "no" blindly. Read the
vote proposal, when it's posted, and think about it.
And _please_ don't go out soliciting "no" votes or "yes" votes from
people who aren't going to read the proposal.
Anthony
--
Anthony Baxter <[EMAIL PROTECTE
You may have noticed I haven't been
> terribly secretive about recent cross site scripting or cache
> poisoning issues, and that can be attributed to, in part, my growing
> disastifaction with the system.
That's really a separate issue that is a zope corp thing to address...
ython/ to enable them, with them
disabled by default.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
d
> writes to happen in a version.
> Am I missing something here?
I think that will only work if there's a Version with the specified name.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
_
Running the current Zope2 HEAD with current-cvs python,
starting gives the following 3 warnings.
/home/anthony/src/zope/ZopeHead/lib/python/ZServer/medusa/test/max_sockets.py:53:
DeprecationWarning: integer argument expected, got float
for i in range(1 + len(sl) * 0.05):
/home/anthony/src/zop
>>> Andreas Jung wrote
> I agree but the current implementation sux. Switching to a counter based
> solution would solve the problem. The only problem I see is to keep the
> code fully backward compatible.
if there's no counter present:
create one, do a count of the docs, initialise the counte
On 9/28/06, Lennart Regebro <[EMAIL PROTECTED]> wrote:
My 0.02 EUR:
I like the idea and aim of ZClasses. However:
I think the implementation makes them more difficult to create than
disk-based classes, which defeats the purpose. I also think that
without exact knowledge of the limitations of ZC
anonymously, but am unable to under 2.2.
I'm getting the feeling (from playing a bit) that the current CVS
new security system requires products to be changed to work again -
would anyone else like to confirm this? Is it deliberate, or will
there be a backwards-compatible mode?
Thank
>>> "Phillip J. Eby" wrote
> >In our case, perhaps it needs to be::
> >
> > def findNearestResource( meta_type ):
> >
> >which causes a walk up the containment hierarchy, searching for objects
> >of the given meta_type.
>
> I would suggest that it ask for an interface, rather than a meta_type.
>
> I tried removing the PythonMethods to see if they were stored in an unusual
> way, and this did not change the behavior...
It's not just you - I've been unable to get any imports to work in
current-cvs.
Anthony
--
Anthony Baxter <[EMAI
aside - should issues with current-cvs go into the Collector?
Many times it seems stuff is fixed well before the Collector gets
seen to.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
1 - 100 of 109 matches
Mail list logo
