[Zope-dev] Debugging help wanted for really weird ZClass problem
I need some debugging help with a problem I've had with 2.4 and ZClasses. I have been completely unsuccessful in tracking this one down so I can reproduce it and file a proper bug report on it. Specifically, while developing ZClasses (occasionally deleting and recreating them, i.e. to change base classes), I will often get to a point where I get a traceback ending in NameError: global name 'ClassName' is not defined I'm using the default constructor DTML method in this case, although a python script yields the same error. I thought I had this trapped in the wild, as I backed up Data.fs with the broken behavior, then exported the ZClass products this particular one depended on, made a new Data.fs, and reimported them. They worked. So then I restored the old Data.fs and it was suddenly working (no amount of packing, restarting, or cleanGlobals-ing could get me this far before, but somehow backing up and restoring Data.fs did...?) I'm really stumped here. Anyone have a clue or three? I'm willing to do some debug legwork if I can catch it again... -- Matt Behrens <[EMAIL PROTECTED]> System Analyst, Baker Furniture ___ 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 )
Re: [Zope-dev] Debugging help wanted for really weird ZClass problem
Got the traceback again today. Here it is: Traceback (innermost last): File /export/home/b14741/Zope_Dev/lib/python/ZPublisher/Publish.py, line 223, in publish_module File /export/home/b14741/Zope_Dev/lib/python/ZPublisher/Publish.py, line 187, in publish File /export/home/b14741/Zope_Dev/lib/python/Zope/__init__.py, line 226, in zpublisher_exception_hook (Object: DevRequest_factory) File /export/home/b14741/Zope_Dev/lib/python/ZPublisher/Publish.py, line 171, in publish File /export/home/b14741/Zope_Dev/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: DevRequest_add) File /export/home/b14741/Zope_Dev/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: DevRequest_add) File /export/home/b14741/Zope_Dev/lib/python/OFS/DTMLMethod.py, line 195, in __call__ (Object: DevRequest_add) File /export/home/b14741/Zope_Dev/lib/python/DocumentTemplate/DT_String.py, line 546, in __call__ (Object: DevRequest_add) File /export/home/b14741/Zope_Dev/lib/python/DocumentTemplate/DT_With.py, line 133, in render (Object: DevRequest.createInObjectManager(REQUEST['id'], REQUEST)) File /export/home/b14741/Zope_Dev/lib/python/DocumentTemplate/DT_Util.py, line 231, in eval (Object: DevRequest.createInObjectManager(REQUEST['id'], REQUEST)) (Info: REQUEST) File , line 2, in f (Object: guarded_getitem) NameError: global name 'DevRequest' is not defined In this case, DevRequest is my ZClass. DevRequest_addForm Id Title Text DevRequest_add I have a complete backup of my Zope install now that has the nonfunctional ZClass. Can anyone help, suggest some steps to take, etc.? -- Matt Behrens <[EMAIL PROTECTED]> System Analyst, Baker Furniture ___ 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 )
DCWorkflow (was Re: [Zope-dev] Another open letter. :-))
Lennart Regebro wrote: > From: "Dieter Maurer" <[EMAIL PROTECTED]> >> > Here are some things that I feel should be introduced into Zope: >> > - Workflow support. (Because everybody needs it) >>You know DCWorkflow? > Yes. I think it should be moved off CMF and into Zope proper. I am actually working on such an animal, but I have no idea when/if I will be able to release the code. My request to the powers that be to be able to release my code is moving very slowly. In the meantime you can use it with a minimalist portal_actions/types/workflow triad with a little patch that's currently sitting in the PTK tracker. Number 401, I think. Sorry, no doco yet :-) ___ 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 )
Re: DCWorkflow (was Re: [Zope-dev] Another open letter. :-))
Stephan Richter wrote: >> I am actually working on such an animal, but I have no idea when/if I >> will be able to release the code. My request to the powers that be to >> be able to release my code is moving very slowly. >> >> In the meantime you can use it with a minimalist >> portal_actions/types/workflow triad with a little patch that's >> currently sitting in the PTK tracker. Number 401, I think. Sorry, no >> doco yet :-) > PLEASE, look at OpenFlow (a Zope Product). It is based on years of > research and covers all aspects. It works very well too! Well, I did, actually, for at least a little bit. Its concept of "tokens" seems to be geared much more towards RDBMS-backed apps, and in some areas seems needlessly complex, at least for the app I'm working on. ___ 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 )
Re: [Zope-dev] Open Letters and Zope 3
Shane Hathaway wrote: > Q: Will Zope 3X be compatible with Zope 2 products? > A: No. What's up with the ZopeLegacy stuff in the co I'm getting now? Yes I am grabbing the branch... > To check out Zope 3X from CVS: > > cvs -d :pserver:cvs.zope.org:/cvs-repository co -r Zope-3x-branch Zope3 :pserver:[EMAIL PROTECTED]:/cvs-repository And don't forget cvs login. > Again, this is all quite exciting and I hope you can join the action. I hope to. Who's in charge of packaging and installation? I see an opportunity to do it right this time, I hope I'm not too late to the party. ___ 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 )
[Zope-dev] Testers needed for z2.py security patch
I've made a security patch for Zope 2.5.0b3 that addresses the setuid startup issues on UNIX and plan to backport it to 2.4.4 (?) and 2.3.3 once I get some positive reports. Only UNIX users need apply this patch. Windows may well have similar issues but I have no clue how to fix them. Please check it out and let me know how it works on your system, or if any clarifications are needed. ___ 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 )
[Zope-dev] Re: Testers needed for z2.py security patch
Matt Behrens wrote: > I've made a security patch for Zope 2.5.0b3 that addresses the setuid > startup issues on UNIX and plan to backport it to 2.4.4 (?) and 2.3.3 > once I get some positive reports. > > Only UNIX users need apply this patch. Windows may well have similar > issues but I have no clue how to fix them. > > Please check it out and let me know how it works on your system, or if > any clarifications are needed. Errr, it's available at <http://www.zope.org/Members/zigg/UnixSecurityPatch>, sorry for any confusion :-) ___ 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 )
Re: [Zope-dev] Re: Python 2.1.2 does not fix the signal 11 crashing problem !!!!!!!!!!!
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 the Zope-2_4-branch from CVS (see http://dev.zope.org/CVS for info). Now leave poor Matt alone :-) ___ 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 )
[Zope-dev] Very, very strange problem with 2_4-branch
After upgrading to 2_4-branch, I started having some problems with
authentication, or so I thought. I have a standard user folder in the
root and an XUF in a top-level folder.
After much wailing and gnashing of teeth, I dug into _check_context, and
added a debug statement, now I have:
def _check_context(self, object):
# Check that 'object' exists in the acquisition context of
# the parent of the acl_users object containing this user,
# to prevent "stealing" access through acquisition tricks.
# Return true if in context, false if not or if context
# cannot be determined (object is not wrapped).
parent = getattr(self, 'aq_parent', None)
context = getattr(parent, 'aq_parent', None)
if context is not None:
if object is None:
return 1
if not hasattr(object, 'aq_inContextOf'):
if hasattr(object, 'im_self'):
# This is a method. Grab its self.
object=object.im_self
if not hasattr(object, 'aq_inContextOf'):
# Object is not wrapped, so return false.
return 0
zLOG.LOG('BasicUser._check_context', zLOG.DEBUG,
'%s.aq_inContextOf(%s, 1) returned %d' %
(object.getPhysicalPath(), context.getPhysicalPath(),
object.aq_inContextOf(context, 1)))
return object.aq_inContextOf(context, 1)
I am getting the following log output:
2002-01-25T16:36:23 DEBUG(-200) BasicUser._check_context ('',
'zope').aq_inContextOf(('', 'zope'), 1) returned 1
and
2002-01-25T16:38:07 DEBUG(-200) BasicUser._check_context ('', 'zope',
'dept', 'is', 'alerts').aq_inContextOf(('', 'zope'), 1) returned 0
Now, the weird part is that this problem is sporadic. It will go away
and reappear with some frequency.
Any ideas? Anyone?
___
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 )
Re: [Zope-dev] Python 2.1.2 causes Error code 6?
stefan holek wrote: > At 28.01.2002 13:55 +, Chris Withers wrote: > >> 1. What does Error Code 6 mean? > > > #define ENXIO6 /* No such device or address */ Bzzt. The error code comes from waitpid(), which the Python library doco says has the same return code as wait(). The low eight bits are a signal, so we actually got a signal 6, not an exit code 6. Signal 6 is SIGABRT. ___ 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 )
Python 2.2 and Makefile.pre.in (was Re: [Zope-dev] Zope under cygwin)
Tony Goodwin wrote: > It appears to be trying to rebuild the python within Zope? There is a > makefile.pre.in > within Zope..src/lib/python, but poiting to it just gives error of form > no target boot in MAkefile Python 2.2 doesn't come with a Makefile.pre.in, which Zope depends on to build the C extensions. I have heard that copying the one from a 2.1 installation will work. I have not yet tried it. I think this is getting to be a FAQ :-) ___ 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 )
Re: [Zope-dev] Zope builds (new Intel C++ compiler)
Matthew T. Kromer wrote: > OK, but be warned -- gcc cvs isnt guaranteed stable, so often I have to > hand tweak things (rebuilding certain modules with different options, etc.) In my experience, *any* gcc can produce crap code if you feed it the wrong options. It may be fun to play with options, but let me just throw in my two cents to this thread -- don't get so excited about your 25% speed gain that you throw it into production to trust your data with. ___ 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 )
Re: [Zope-dev] how can i add index_html
sushant wrote: > hi, > i just wanted to know how can i publish my product in zope.org. > > as i have put it there(in software product) but i am unable to add > index_html, can you pls > suggest. how to add index_html into it. You really shouldn't be putting index_html into software products themselves. Software products already know how to render themselves; just set the appropriate properties. You can put an index_html into your home directory (which you probably already know) :-) ___ 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 )
[Zope-dev] sre and import_class
re seems to prefer sre over pre these days, so the following bit of Products/PythonScripts/module_access_examples.py no longer works: # from re import RegexObject, MatchObject # allow_class(RegexObject) # allow_class(MatchObject) The reason seems to be that sre doesn't define RegexObject and MatchObject, preferring instead to define types SRE_Pattern and SRE_Match, which can't be imported. Arguably this is probably a deficiency in sre, but as it stands, it seems to be currently impossible to use re inside of python scripts. I'm using an EM. I'll file a Collector issue on this one, unless someone has a solution, or someone wants to just take the 're' section out of module_access_examples.py. ___ 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 )
Re: [Zope-dev] Zope 2.6 project updated
Christian Theune wrote: > Well I saw the cookie crumbler wish has been added to the list already, > and (as i tested it out this moment) don't see what exactly needs to > be done than adding it by default to the root userfolder. > Well, probably some facelifting to the default login, thats not > urgent in any way but if wished i would do that. Well, as far as "least-intrusive", CC loses some points by not being compatible with some of the user folders that do their own cookie auth, although that's arguably not CC's fault. ___ 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 )
Re: [Zope-dev] Cookie Crumbler and similar products (Re: Zope 2.6 project updated)
Christian Theune wrote: > Hmm. I didn't get an answer right now (well i don't find the question again too) > if the cookie crumbler would interfere subfolders (distor through acquisition) > or would only be active on a "sibling" userfolder, which he is "watching". I'm really not sure. I imagine it could be troublesome. ___ 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 )
Re: [Zope-dev] User Folders
Chris Withers wrote: > Right now, I'd like to see the scope kept _tight_, just dealing with > authentication, no user metadata, that can wait for later. There is XUF, but I'm > not sure about the code quality and I think it tries to do too much. > > Of course, I could be wrong... Speaking as someone who's worked on parts of the code, I don't think you're wrong. XUF has issues that I'm not sure anyone really understands, though my recent "exploding user object" cache work got it to the point where it does seem to be stable on heavily-loaded systems. Yes, it does try to do too much, I think. Back before I figured out enough of XUF to fix the cache issues I played around a bit with a virginal pluggable user folder (right now it does not do much of anything, including authenticate, but it is a beginning.) I still have the code, and my boss would still like to see it brought to fruition. I do have quite a bit to say about the design of such an animal. It's something we need. > In any case, I'd be happy to monitor a discussion to build a solution to this (I > might even be persuaded to strike up a fishbowl process ;-) and get the finished > product done. I dunno if I could manage it for 2.6, but I'd certainly get it > done for 2.7... I held back on suggesting this because I'm not convinced I have the resources or the ability to bring this baby up on my own, and especially not in time for 2.6. But if others are interested in _contributing_, everyone can count me in too, I'm sure (although how much time I have to offer is up in the air as other projects are starting to pound on my door...) ___ 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 )
Re: [Zope-dev] Bug days
Brian Lloyd wrote: > In an effort to better keep up with the collector, I'd like > to throw out the idea of doing periodic "bug days" (a la > the mozilla bug days), where Zope geeks and committers would > get together on IRC and spend a few hours knocking out issues. Yes, this would be *very* cool, if for no other reason than to try to thin out the Collector. I made one pass over it today and found a few that never got closed when resolved, etc. What several of them seemed to fall into, though, were ones that really merited a discussion of some sort to resolve, preferably with a senior engineer of some sort present to at least bounce ideas off. > - Given the wide geographic area that committers (and patch > submitters) cover, what is a good time of day for a bug > day to start / end (where start and end are always going > to be fuzzy, of course). I'm sure I could swing a weekday every once in awhile (during the workday, EST) at work. > - Would it be better for bugdays to be ad-hoc, or should we > try to set up regularly-scheduled bugdays at some reasonable > interval? If the latter, we need to come up with a day / time > that is agreeable to as many of the committers as possible. Better make 'em scheduled, or no-one will show. :-) ___ 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 )
Python 2.2 (was Re: [Zope-dev] Zope 2.6 planning - call for contributors!)
Lennart Regebro wrote: > Are you planning to up the python version to 2.2? Because in that case I'd > be happy to put in Authentication support in MailHost. Smtplib.py in 2.1.2 > doesn't support authentication. I don't know how people are currently using Zope with 2.2. There is probably some really nasty problem being masked by the platform (seems to be Linux). See http://collector.zope.org/Zope/200 -- there's at least problems on Solaris and OpenBSD, probably others. ___ 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 )
Re: [Zope-dev] Umask? On Windows 98? Ha!
Lennart Regebro wrote: > I get this message when starting Zope 2.5.1b1 on Windows 98: No you didn't, you got it on the trunk. I just double-checked. My big security patch was never checked in on the 2.5 branch. > 2002-03-18T19:32:15 INFO(0) z2 Your umask of 000 may be too permissive; for > the > security of your Zope data, it is recommended you use 077 > > That's rather silly on Windows 98. :-) I agree. I noticed this over the weekend and am testing a few more scenarios. I mistakenly assumed that os.umask wouldn't exist on non-POSIX systems, so the try: block would cover it. But instead, os.umask says 0. > A couple of questions: > - Should that really be 077? That means that the owner can't read the files, > but that "other" can! How can that be less permissive? 770 would make sense > to me. I usually run z2.py with -u zope, and have zope own the files, and > letting nobody else do scrap with them, 700, in other words. WHy would 077 > be better? First, if you don't start the number with 0, it's not octal. Second, you are confusing umasks with modes. When you create a file on UNIX its modes are 0666 & umask, directory 0777 & umask. Thus, creating a file with umask 077 results in mode 0600 (read/write only for owner). The default UNIX umask is 022, which results in a Data.fs that is readable by all. You can twiddle permissions on it, sure, but it'll turn up readable by all again when you pack the database. > - Is it silly to check for Windows? What happens on Windows NT, does that > emulate umask somehow, or do you get 000 there too? Yes, but it's not silly to check for os.name == 'posix', which I will fix on my own time later, prob. tonight. ___ 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 )
Re: [Zope-dev] Asia To USA Shipping Rates
[EMAIL PROTECTED] wrote: > We have a full collection of wholesale freight rate calculators at > > http://www.apx-air-cargo.com > > Our new calculator is here and it will calculate rates from Asia to over 30 US >cities including customs clearance and delivery. Great! Is it available as a Product? Can I use it with Z3? > CLICK HERE http://www.freight-calculator.com/ocean-asia/oceanasia.asp Oh, darn, I guess not. :-) ___ 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 )
Re: [Zope-dev] Moving forward on Zope 2.6
Florent Guillaume wrote: > Okay, I'm a bit late but I'd like to integrate what's currently in > NuxUserGroups, a bit updated maybe. > > http://www.zope.org/Members/nuxeo/Products/NuxUserGroups > > There will be a merge conflit with Lennart's Local roles blacklists, > it it's chosen for 2.6, but I'm familiar enough with both code sets to > manage the merge. > > I'm adding this proposal to the wiki. I do recall that we looked at NUG as XUFers at at one point, and akm said it looked like it'd be compatible, although we still needed UI for groups in XUF. Nobody has done this, incidentally. :-) I'm not convinced that it'll go so well with other user folders. My gut feeling is that while groups are a very, very good thing (we NEED them here), and I'd love to see them in Zope 2, I think the issue of compatibility with all the other user folders out there is going to be a huge sore spot. So, -1, unless you can prove to me that every user folder on zope.org that hasn't already been obsoleted due to Zope changes will also work with NUG integrated (and the unfortunate fact that everyone probably has to change UI probably makes that a non-issue.) This coming from a guy who really wants groups. :-/ ___ 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 )
Re: [Zope-dev] Next steps on Zope 2.6 plan
Brian Lloyd wrote: > One suggestion Casey had was to start to codify a set of rules > that features have to abide by to be considered for inclusion. Hmm, these rules seem to have several thinly veiled references to my pet project. :-) I do firmly agree with the rules in spirit, but I think a little clarification/discussion is in order so it doesn't get cut without good reason. > - A feature release should never contain more than one blow-it- > up-and-redo-it type project (such as radical changes to key > parts of packaging or infrastructure). For example, it would > probably be a bad idea to totally redo the ZODB, packaging > and installation and the security system all in one release > (unless it is a major release like Zope2 -> Zope3). Agreed. I think it is important to note two things, though: 1. Creating the new, recommended installation procedure is different from gutting and replacing an existing feature, simply because we don't really *have* a recommended installation procedure right now. As currently proposed, you can still use Zope 2.6 just like you used Zope 2.5, except you'll type 'make' instead of 'python2.1 wo_pcgi.py'. 2. I've tried to keep this proposal clean enough that it can easily be brought into Z3, so that instances of Z2 and Z3 on the same system can be controlled and managed by the same software. > The aggregate impact in terms of obsoleting existing knowledge > and documentation is too great to do many of these at once. It > takes time for users and developers to catch up after something > major is refactored, and we need to keep this in mind. Just to reiterate, they'll have all the time they need. The only people I see scrambling to get up to date are Zope 2.6 packagers (like myself). Perhaps a qualification is in order here, i.e. mitigation of this effect by maintaining as much backwards compatibility as possible. > - Features or components added to the Zope core should address a > clear and generally agreed-upon need. Otherwise, accumulation > of components over time will become a significant support > burden for the zope maintainers. My proposal will probably reduce support burdens. Just the other day, on IRC, we had to tell someone to switch away from his nicely packaged RPM version of Zope and use the source distro. So maybe this should be a qualified rule as well? > Thoughts? I'll volunteer to maintain the guidelines document > on dev.zope.org if folks can send their guideline suggestions. I don't know if the above constitutes useful information for writing rule changes or not, but I hope it's helpful. ___ 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 )
Re: [Zope-dev] ZClass Constructor Cleanup for 2.6
Casey Duncan wrote: > Does anyone see a problem with changing the default generated > constructor method for ZClasses to a python script in Zope 2.6? > > I think we are encouraging really bad style by keeping this in DTML, > since it is purely business logic. > > Thoughts? I will, of course, implement this if nobody objects. +2 (I'm taking Andreas' vote because he says 'zclasses sux' and 'zclasses must die', so he's biased) ___ 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 )
ZCatalogPathAware (was Re: [Zope-dev] ZClass Constructor Cleanup for 2.6)
Leonardo Rochael Almeida wrote: > ZClasses have been overlooked enough. Nobody has even bothered putting a > ZCatalogPathAware available for them... I tried do to this quickly for someone on IRC once. The problem is that the mixin is identically named for CatalogAwareness and CatalogPathAwareness, and as such they show up looking exactly the same in the ZClass mixin list. :-) There's probably a way around this that wasn't immediately obvious at the time. ___ 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 )
Re: [Zope-dev] can't put in dtml
[For future reference, questions like this one should go to [EMAIL PROTECTED] [EMAIL PROTECTED] is for discussion of development of Zope. Replies/followups directed there.] Yuan-Chen Cheng wrote: > Can't put in dtml, but > is okay. The
[Zope-dev] Overriding HTTPResponse.unauthorized()
I've got some rather funky auth requirements where I need to stop Zope from challenging Basic authentication when Unauthorized is raised. I seem to be able to do this if I monkey-patch HTTPResponse.unauthorized(), but what I'd really like is to be able to hook into it to make a user folder-overridable challenge with a fallback to the standard unauthorized. Maybe such a hook would be useful in 2.6 :-) So, given that, can I get to the user folder from HTTPResponse.unauthorized()? Or are there any better ideas? ___ 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 )
Re: [Zope-dev] Re: 2.3.3 -> 2.5.1b2 upgrade problem
Simon Michael wrote: > "R. David Murray" <[EMAIL PROTECTED]> writes: >>Probably, but I naively imagined that I was sophisticated enough >>to be finding a "real" problem...but I'm obviously not smart enough >>to realize that a breakage this fundamental could be due to a package >>like ZDebug. > I wasn't either.. I think the word is getting around now, but it would be > great to see ZDebug updated to work with newer zope versions. I really > miss it. And Formulator :-) ___ 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 )
Re: [Zope-dev] Zope crash & restart
Myroslav Opyr wrote: > System Platform > freebsd4 Are you running with the pthread stack size patches applied to Python? See https://sourceforge.net/tracker/?func=detail&aid=554841&group_id=5470&atid=305470 for the patch, and recompile Python with OPT="-g -O2 -DTHREAD_STACK_SIZE=0x2" ./configure --whatever-your-options-are ___ 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 )
Re: [Zope-dev] Zope crash & restart
Myroslav Opyr wrote: > As far as I remember the issue was solved in Python 2.1.3, wasn't it? Or > it was GC patch? No. Try my patch, that solves the problem Jens is talking about. ___ 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 )
[Zope-dev] help system and .py files
Is it at all productive to have .py files in the help system byte-compiled? ___ 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 )
Re: [Zope-dev] ExternalEditor & Windows
brian.r.brinegar.1 wrote: > I've started a VB Script version for the Windows Scripting Host. Right now > I'm in the proof of concept stage. I've got something that opens a file, > spawns an editor, gets the process id, and can PUT a file to Zope. (works > with SSL too) Please pardon my Windows ignorance, but does using WSH mean that IE will be required to be used? ___ 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 )
Re: [Zope-dev] Python, Zope and pymalloc
Dario Lopez-Kästen wrote: > Is anyone using zope with a python that is not configured with > --without-pymalloc ? > > I understand that there is still a conflict with ExtensionClass unless > python is cfg'd --without-pymalloc? You are correct, sir. ExtensionClass is not pymalloc-safe, so saith the Kromer. This is not to say it could not be made so. ___ 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 )
[Zope-dev] Bug Day for June?
Are we having a Bug Day on Friday? ___ 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 )
Re: [Zope-dev] Crash & Burn with Zope 2.6.0a1 and ZEO 2.0a1
Stefan H. Holek wrote: > Z2.pid is created very late. I cannot ./stop a half-started Instance > (not even a ZEO client waiting for the server!). Could we create the pid > file earlier? Actually Z2.pid *is* now created earlier than with 2.5.1, the setuid stuff for root startups was moved after the Z2.pid creation to stop a potential security issue. I don't see any reason it couldn't be created before the servers are started, however. Others may have reasons why. ___ 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 )
Re: [Zope-dev] Error by using libraries with an external method
Dario Lopez-Kästen wrote: > From: "Leonardo Rochael Almeida" <[EMAIL PROTECTED] >>Putting it in the Extesions directory, so that it can be imported by >>external methods, doesn't seem to work, even if you put Extensions in >>the PYTHONPATH, at least in my experience. > hm... Putting it in the Extensions directory has worked for me using Zope > 2.4.3 (I don't like to mess with the PYTHONPATHG in the Python Install)... > Has this changed in later zopes? What's wrong with twiddling PYTHONPATH? My instance home has a 'Packages' directory, where I have stuff like _ldapmodule.so (for ZLDAP), imaging.so, and the PIL and ldap packages. My start script looks like this: #!/bin/sh PYTHON_VER=2.1.3 ZOPE_VER=2.5.1 INSTANCE_HOME=/zope PYTHONPATH=$INSTANCE_HOME/Packages export INSTANCE_HOME PYTHONPATH STUPID_LOG_FILE=$INSTANCE_HOME/var/log/zlog_`date +%Y%m%d`.log STUPID_LOG_SEVERITY=-200 export STUPID_LOG_FILE STUPID_LOG_SEVERITY echo `date` starting >> $INSTANCE_HOME/var/log/start_`date +%Y%m%d`.log exec $INSTANCE_HOME/Python-$PYTHON_VER/bin/python2.1 \ $INSTANCE_HOME/Zope-$ZOPE_VER/z2.py \ -F $INSTANCE_HOME/var/FastCGI.soc -m 8099 -p - "$@" \ >> $INSTANCE_HOME/var/log/start_`date +%Y%m%d`.log 2>&1 All in all, it works pretty well. No need to sweat messing with PYTHONPATH. All instance homes should do this, and have a Packages directory :-) ___ 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 )
[Zope-dev] Bug Day 8/02 recap
Zope Bug Day August 2002 was an unqualified success, with our largest bug total squashed to date: 45! The number of still-open collector issues dropped by almost 25%. Thanks to all those who participated! More information on Zope Bug Days can be found at http://dev.zope.org/CVS/BugDays. I think it would be good to hold another one in September; how's the 11th at 9 AM US/Eastern? (For the curious, we squashed #101, #115, #121, #46, #129, #27, #297, #29, #148, #461, #497, #38, #501, #106, #453, #69, #37, #40, #74, #95, #82, #507, #53, #168, #408, #81, #83, #90, #93, #104, #113, #61, #117, #127, #132, #134, #152, #268, #192, #13, #92, #179, #177, #518, AND #332.) -- Matt Behrens <[EMAIL PROTECTED]> ___ 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 )
Re: [Zope-Coders] Re: [Zope-dev] Bug Day 8/02 recap
On Fri, Aug 16, 2002 at 09:58:38AM +0100, Chris Withers wrote: > Well, there were a lot of 'rejected' issues and a fair few deferals too. > I'm mildly concerned about some of those rejections being premature and > some of the deferals being used just to bury stuff 'cos no-one has time to > deal with them right now. Yes, there were a lot of rejections. Out of the ones I myself made, most were due to the bug report being invalid -- that happens a *lot* with any issue reporting system. Several also had to be dumped because more info was asked for six months ago and never received. We discussed most of them on IRC, which was truly the real benefit of having a Bug Day: getting that rough consensus needed to take action. I also made several resolutions, most of which were bugs that were fixed before, advertently or inadvertently. Very little code was checked in; most resolutions seemed to be bugs that had already disappeared for one reason or another. I consider this a good thing. :-) -- Matt Behrens <[EMAIL PROTECTED]> http://zigg.com/> msg5/pgp0.pgp Description: PGP signature
