AW: [Zope-dev] Re: [Zope3-Users] How do I automatically login a user
Ha David Betreff: Re: [Zope-dev] Re: [Zope3-Users] How do I automatically login a user Thanks Jim for doing this. Actually, the domain is something I have been looking for also. These other features are really nice. I am hoping this can be worked into something like z3c.authentication for generic use. Hoping roger is following this. Yes, yes, just found no time to pickup this. But it's on the top of my 1000 things to do list ;-) Note: I started to make progress with z3c.authenticator. This will become a replacement for z3c.authentication.simple Does anybody think we will need a migration script? Regards Roger Ineichen _ END OF MESSAGE Regards, David Jim Fulton wrote: Let's move this discussion to zope-dev. On Apr 2, 2008, at 5:36 AM, kevin gill wrote: Please check in the code to the sandbox and I will have a look at it. The coding looks straight-forward, but choosing how to work it into the existing components. I will look at the code and come back with questions. I just checked 2 files, session.txt and session.py, into http://svn.zope.org/Sandbox/J1m/ These provide several features, most of which are of particular interest here: - An api to save session credentials independent of login, - saving sha-encoded passwords, - logout api - having an optional additional credential of a user domain, (probably not of general interest) Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org 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 ) ___ Zope3-users mailing list [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Thu Apr 3 11:00:00 2008 UTC to Fri Apr 4 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu Apr 3 20:57:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009350.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Apr 3 20:58:45 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009351.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Apr 3 21:00:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009352.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Apr 3 21:01:45 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009353.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Apr 3 21:03:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009354.html ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] testing a meta-egg
Hello, Is there a sane way (or recipe) out there that makes testing a meta-eggs easier? As I see now, I'll need to enter all dependent eggs as: [test] recipe = zc.recipe.testrunner eggs = my-meta-egg [test] dep-egg-1 [test] dep-egg-2 [test] ... zope.interface [??test??] Seems like buildout knows which eggs should be there. This would be needed for a pre-installation test on the target system. We need to make sure that all tests pass before going into production. Any help is appreciated. -- Best regards, Adam GROSZER mailto:[EMAIL PROTECTED] -- Quote of the day: Talk sense to a fool and he calls you foolish. - Euripides ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Re: GSoC proposal
Malthe Borch wrote: On 04/04/2008, Chris Withers [EMAIL PROTECTED] wrote: zope.security uses RestrictedPython, iirc... For untrusted python, yes –– but is anyone using this (in Zope 3)? It's integral to most Zope 2 applications of course to allow secure execution of Python scripts, so we will need to port RestrictedPython eventually. Btw, it would also be nice to have RestrictedPython outside of Zope for example to use in pl/python (postgres pluggable function language) Of course this smells like another GSoC project... Greets Tino ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] testing a meta-egg
On Apr 4, 2008, at 7:14 AM, Adam GROSZER wrote: Hello, Is there a sane way (or recipe) out there that makes testing a meta-eggs easier? As I see now, I'll need to enter all dependent eggs as: [test] recipe = zc.recipe.testrunner eggs = my-meta-egg [test] dep-egg-1 [test] dep-egg-2 [test] ... zope.interface [??test??] Seems like buildout knows which eggs should be there. This would be needed for a pre-installation test on the target system. We need to make sure that all tests pass before going into production. Any help is appreciated. IMO, testing the dependent eggs isn't desirable, however, I don't object to providing an option to do it. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re[2]: [Zope-dev] testing a meta-egg
Hello Jim, Friday, April 4, 2008, 2:22:06 PM, you wrote: JF IMO, testing the dependent eggs isn't desirable, however, I don't JF object to providing an option to do it. How do you propose or in fact how do you do testing just before going into production? Would you please give some hints how to dig that information out in he recipe? JF Jim JF -- JF Jim Fulton JF Zope Corporation -- Best regards, Adam GROSZERmailto:[EMAIL PROTECTED] -- Quote of the day: Would you tell me, please, which way I ought to go from here? That depends a good deal on where you want to get to, said the Cat. - Lewis Carrol ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: Re[2]: [Zope-dev] testing a meta-egg
On Apr 4, 2008, at 8:55 AM, Adam GROSZER wrote: Hello Jim, Friday, April 4, 2008, 2:22:06 PM, you wrote: JF IMO, testing the dependent eggs isn't desirable, however, I don't JF object to providing an option to do it. How do you propose or in fact how do you do testing just before going into production? For individual packages, I assume that they were tested before release. I prefer to test just the software I'm working on. Of course, I have integration tests of my application. Would you please give some hints how to dig that information out in he recipe? I wouldn't want anyone doing this who wasn't willing to spend the time becoming fairly familiar with the setuptools APIs. The full set of packages uses is described by the working set, which is available (or obtainable) to the recipe. To include tests of all dependencies, you would include each of the locations from the working set as test directories for the test t runner, being careful to avoid system packages -- unless you want to test all system packages on which you depend too. Even then, you could get into trouble, as individual package tests might not be runnable without additional facilities you don't have. For example, some packages might have test dependencies that you haven't included. There is no standard way of specifying test dependencies for installed distributions. In general, I find implicitly including packages for testing is fraught with peril. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re[4]: [Zope-dev] testing a meta-egg
Hello Jim, Sounded like a good idea at first, but now you opened my eyes. I guess I'll stick with the manually added eggs for the tests. Thanks. Friday, April 4, 2008, 3:08:27 PM, you wrote: JF I wouldn't want anyone doing this who wasn't willing to spend the time JF becoming fairly familiar with the setuptools APIs. The full set of JF packages uses is described by the working set, which is available (or JF obtainable) to the recipe. To include tests of all dependencies, you JF would include each of the locations from the working set as test JF directories for the test t runner, being careful to avoid system JF packages -- unless you want to test all system packages on which you JF depend too. Even then, you could get into trouble, as individual JF package tests might not be runnable without additional facilities you JF don't have. For example, some packages might have test dependencies JF that you haven't included. There is no standard way of specifying JF test dependencies for installed distributions. JF In general, I find implicitly including packages for testing is JF fraught with peril. -- Best regards, Adam GROSZERmailto:[EMAIL PROTECTED] -- Quote of the day: Only God can make random selections. ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] zope.rdb problem (as it looks)
Hello,
We're having here a problem in a high load situation with quite long
running (10-20 secs) transactions.
The app uses mySQL extensively, and just a bare minimum of ZODB to
store the root and registrations.
I think that there's lower level error concerning ZODB, but in
zope.rdb, in queryForResults, line 381:
except Exception, error:
eats the traceback.
This smells like
https://bugs.launchpad.net/zope3/+bug/98331
So I propose to move that except further down the stack, where it will
really catch just DB errors.
Or any better idea is welcome.
Module zope.publisher.publish, line 133, in publish
result = publication.callObject(request, obj)
Module zope.app.publication.zopepublication, line 161, in callObject
return mapply(ob, request.getPositionalArguments(), request)
Module zope.publisher.publish, line 108, in mapply
return debug_call(obj, args)
__traceback_info__: security proxied
zope.app.publisher.browser.viewmeta.ManagementViewSelector instance at
0x48822a0c
Module zope.publisher.publish, line 114, in debug_call
return obj(*args)
Module zope.app.publisher.browser.managementviewselector, line 35, in __call__
item = getFirstMenuItem('zmi_views', self.context, self.request)
Module zope.app.publisher.browser.menu, line 181, in getFirstMenuItem
items = getMenu(id, object, request)
Module zope.app.publisher.browser.menu, line 176, in getMenu
return menu.getMenuItems(object, request)
Module zope.app.publisher.browser.menu, line 53, in getMenuItems
if item.available():
Module zope.app.publisher.browser.menu, line 113, in available
view = traverser.traverseRelativeURL(
Module zope.app.publication.browser, line 47, in traverseRelativeURL
ob = self.traversePath(request, ob, path)
Module zope.app.publication.publicationtraverse, line 95, in traversePath
ob = self.traverseName(request, ob, name)
Module zope.app.publication.publicationtraverse, line 61, in traverseName
ob2 = adapter.publishTraverse(request, nm)
Module zope.app.container.traversal, line 72, in publishTraverse
return self.context[name]
Module container, line 65, in __getitem__
if not self.__contains__(key):
Module container, line 111, in __contains__
results = queryForResults(db,query)
Module zope.rdb, line 384, in queryForResults
raise DatabaseException(str(error))
DatabaseException: Shouldn't load state for 0x50 when the connection is closed
--
Best regards,
Adam GROSZER mailto:[EMAIL PROTECTED]
--
Quote of the day:
Major Premise: Sixty men can do a piece of work sixty times as quickly as one
man.
Minor Premise: One man can dig a posthole in sixty seconds;
Conclusion: Sixty men can dig a posthole in one second.
___
Zope-Dev maillist - Zope-Dev@zope.org
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 )
Re: [Zope-dev] zope.rdb problem (as it looks)
On Fri, Apr 04, 2008 at 08:36:30PM +0200, Adam GROSZER wrote:
Hello,
We're having here a problem in a high load situation with quite long
running (10-20 secs) transactions.
The app uses mySQL extensively, and just a bare minimum of ZODB to
store the root and registrations.
I think that there's lower level error concerning ZODB, but in
zope.rdb, in queryForResults, line 381:
except Exception, error:
eats the traceback.
This smells like
https://bugs.launchpad.net/zope3/+bug/98331
So I propose to move that except further down the stack, where it will
really catch just DB errors.
Or any better idea is welcome.
This has come up previously:
http://www.nabble.com/zope.rdb-error-and-zope.publisher-error-td10199840.html
Module zope.publisher.publish, line 133, in publish
result = publication.callObject(request, obj)
Module zope.app.publication.zopepublication, line 161, in callObject
return mapply(ob, request.getPositionalArguments(), request)
Module zope.publisher.publish, line 108, in mapply
return debug_call(obj, args)
__traceback_info__: security proxied
zope.app.publisher.browser.viewmeta.ManagementViewSelector instance at
0x48822a0c
Module zope.publisher.publish, line 114, in debug_call
return obj(*args)
Module zope.app.publisher.browser.managementviewselector, line 35, in __call__
item = getFirstMenuItem('zmi_views', self.context, self.request)
Module zope.app.publisher.browser.menu, line 181, in getFirstMenuItem
items = getMenu(id, object, request)
Module zope.app.publisher.browser.menu, line 176, in getMenu
return menu.getMenuItems(object, request)
Module zope.app.publisher.browser.menu, line 53, in getMenuItems
if item.available():
Module zope.app.publisher.browser.menu, line 113, in available
view = traverser.traverseRelativeURL(
Module zope.app.publication.browser, line 47, in traverseRelativeURL
ob = self.traversePath(request, ob, path)
Module zope.app.publication.publicationtraverse, line 95, in traversePath
ob = self.traverseName(request, ob, name)
Module zope.app.publication.publicationtraverse, line 61, in traverseName
ob2 = adapter.publishTraverse(request, nm)
Module zope.app.container.traversal, line 72, in publishTraverse
return self.context[name]
Module container, line 65, in __getitem__
if not self.__contains__(key):
Module container, line 111, in __contains__
results = queryForResults(db,query)
Module zope.rdb, line 384, in queryForResults
raise DatabaseException(str(error))
DatabaseException: Shouldn't load state for 0x50 when the connection is closed
--
Best regards,
Adam GROSZER mailto:[EMAIL PROTECTED]
--
Quote of the day:
Major Premise: Sixty men can do a piece of work sixty times as quickly as one
man.
Minor Premise: One man can dig a posthole in sixty seconds;
Conclusion: Sixty men can dig a posthole in one second.
___
Zope-Dev maillist - Zope-Dev@zope.org
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 )
--
Brian Sutherland
___
Zope-Dev maillist - Zope-Dev@zope.org
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 )
[Zope-dev] IPasswordManager dependencies
Hi all I whould like to move the IPasswordManager interface and the global managers from zope.app.authentication to zope.password. The reason is I don't need the zope.app.authentication implementation but the password manager is used in zope.app.security which makes this and I guess other packages depending on zope.app.authentication. Does somebody see a good reason not to move the password manager part out of zope.app.authentication? Regards Roger Ineichen _ END OF MESSAGE ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] zope 3 docs overview
Hi all, I made a first pass at surveying current Zope 3 docs, at http://wiki.zope.org/zope3/DocsOverview . I think this is more complete and current than other lists I've seen. I hope to keep improving it and use it to guide or possibly just replace other wiki docs. Feedback and help would be welcome. Best, -Simon ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
