Re: [Zope-Checkins] SVN: Zope/branches/philikon-zope32-integration/ start cleaning out the trash; there is more...
On 10/30/05, Chris McDonough [EMAIL PROTECTED] wrote: Will there be a way to keep your srcdir pristine by running ../path/to/configure; make; make install in an empty directory? This was a commonly requested feature and lots of people use it, which is why build-base and friends were in there. Not with the checkout and the current zpkg. I do consider this an unfortunate limitation in the implementation of zpkg; some of the decisions in the implementation will need to change to make it work differently, but I think it's really a matter of implementation and not the basic design. Distributions still allows all the distutils magic to happen, so out-of-place builds should be entirely possible with the packaged distribution. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Society attacks early, when the individual is helpless. --B.F. Skinner ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ - stitched in manage_interfaces from Five
Log message for revision 39892:
- stitched in manage_interfaces from Five
Changed:
U Zope/trunk/doc/CHANGES.txt
U Zope/trunk/lib/python/OFS/SimpleItem.py
-=-
Modified: Zope/trunk/doc/CHANGES.txt
===
--- Zope/trunk/doc/CHANGES.txt 2005-11-04 16:59:20 UTC (rev 39891)
+++ Zope/trunk/doc/CHANGES.txt 2005-11-04 17:24:49 UTC (rev 39892)
@@ -26,6 +26,11 @@
Features added
+ - interfaces: Added 'Interfaces' tab to basic core objects.
+This is a Five feature and only available if the classes are made
+five:traversable. It allows to inspect interfaces and to assign
+marker interfaces through the ZMI.
+
- webdav: Added support for the z3 WriteLock interface.
It is no longer necessary to have the WriteLockInterface in the
__implements__ list of lockable objects. All classes inheriting from
Modified: Zope/trunk/lib/python/OFS/SimpleItem.py
===
--- Zope/trunk/lib/python/OFS/SimpleItem.py 2005-11-04 16:59:20 UTC (rev
39891)
+++ Zope/trunk/lib/python/OFS/SimpleItem.py 2005-11-04 17:24:49 UTC (rev
39892)
@@ -122,6 +122,8 @@
manage_options=(
App.Undo.UndoSupport.manage_options
+AccessControl.Owned.Owned.manage_options
++({'label': 'Interfaces',
+ 'action': 'manage_interfaces'},)
)
# Attributes that must be acquired
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-Coders] Re: SVN: Zope/trunk/lib/python/Testing/ZopeTestCase/ transaction.commit(1) is deprecated in favor of transaction.savepoint().
Thank you for the clarification, Tim. On 3. Nov 2005, at 16:22, Tim Peters wrote: The full deprecation msg spells it out in more detail: subtransactions are deprecated; instead of transaction.commit (1), use transaction.savepoint(optimistic=True) in contexts where a subtransaction abort will never occur, or sp=transaction.savepoint() if later rollback is possible and then sp.rollback() instead of transaction.abort(1) Last time *I* saw it, it said subtransactions are deprecated; use transaction.savepoint() instead of transaction.commit(1) ;-) So, either way, the current code is a bit off target. Best guess is that you're not interested in *sub*transaction aborts here, so that you do want to pass optimistic=True. This is correct. I will pass True then. Stefan -- Anything that happens, happens. --Douglas Adams ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
[Zope-Coders] Zope tests: 7 OK
Summary of messages to the zope-tests list. Period Thu Nov 3 12:01:01 2005 UTC to Fri Nov 4 12:01:01 2005 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:01:27 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003478.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:02:58 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003479.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:04:28 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003480.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:05:58 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003481.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:07:28 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003482.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:08:58 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003483.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:10:28 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003484.html ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
[Zope-Coders] Why zope-coders?
Do we really need this list? In theory, this list is supposed to be about repository-management issues, but that isn't what the traffic has really been about. It has occasional messages about Zope development issues and lots of output from a nightly test runner. I propose to retire this list and move the traffic over to zope-dev. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
Re: [Zope-Coders] Why zope-coders?
On 11/4/05, Jim Fulton [EMAIL PROTECTED] wrote: I propose to retire this list and move the traffic over to zope-dev. I always wondered why this was a separate list. +1 on its retirement. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Society attacks early, when the individual is helpless. --B.F. Skinner ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
[Zope-dev] Re: zope.app stitching
Jim Fulton wrote: We need to stitch zope.app into Zope 2 more carefully than we are now. Much of what we are stitching is unreleased in Zope3 and depends on things not stitched nto Zope 2. Among other things, this means that we can't use python2.4 test.py -m. to run all tests without getting test failures. It would be great if someone would sort this out before we do any Zope 2.9 releases. :) Well, from that vague we need to do it more carefully I deduce that you would like to stitch in zope.app like we stitch in zope, i.e. each package individually. Unfortunately, that will not work equally well because there are several text files at zope.app, more than just the __init__.py: DEPENDENCIES.cfg PACKAGE.cfg PUBLICATION.cfg browser.zcml configure.zcml content_types.py datetimeutils.py decorator.py ftesting.zcml menus.zcml meta.zcml servicenames.py timezones.py At least the Python modules and zpkgutils files will be needed in Zope 2 as well. The real problem is that svn:externals doesn't work on files, just on directories. So, we'd have to manage separate copies of those files. Are you sure we want to get into that? Philipp ___ 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] Re: RFC: product initialization cleanup and improvements
Hi! Some things turned out a bit different than proposed, so I want to report back: 1.) 'action' key: - I'd like to give empty 'action' values a special meaning: The meta_type is not visible in the add drop down in the ZMI. The five:registerClass directive allows to set empty 'action' values. This would resolve http://www.zope.org/Collectors/Zope/1885 . Filtering out meta_types with empty 'action' values is a two line change in main.dtml. I'd like to make that change also on the 2.8 branch to enable that feature for 2.8.5 with Five 1.2. I wasn't able to finish this because it depends on http://www.zope.org/Collectors/Zope/1774 . See my comment in http://www.zope.org/Collectors/Zope/1885 for details. 2.) 'interfaces' key: - Does currently only contain oldstyle interfaces. The code in OFS.ObjectManager that uses that key works also with z3 interfaces. I'd like to add z3 interfaces to the value of that key. That would e.g. allow to set only new style interfaces on catalog index classes. Done. 3.) 'product' key: -- AFAICS it isn't used in Zope itself. I'd like to add a note that it might be removed in a future version. That key is not required, but I found two places in Zope where it is used if it exists: In ProductRegistry for TTW products and in OFS.Application for refreshing products. 4.) related cleanup: Application.install_product has some backwards compatibility code for products that have initialization code outside the 'initialize' method of their __init__.py. This is deprecated at least for 5 years. I'd like to add explicit deprecation warnings on the 2.8 branch and to remove that code for Zope 2.9. Done. Made sure ZGadflyDA and ZSQLMethods don't use the deprecated code. Given the fact that 2 Zope core products still used that code and given the feedback on this list I didn't remove the code in Zope 2.9. This should be done in Zope 2.10 instead. Cheers, Yuppie ___ 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] isDavCollection vs. isAnObjectManager
Hi! Is there any good reason why a true 'isAnObjectManager' makes an object a DAV collection? I'd like to check in this small patch on the trunk: Index: PropertySheets.py === --- PropertySheets.py (revision 39879) +++ PropertySheets.py (working copy) @@ -533,8 +533,7 @@ def dav__resourcetype(self): vself=self.v_self() -if (isDavCollection(vself) or -getattr(aq_base(vself), 'isAnObjectManager', None)): +if isDavCollection(vself): return 'n:collection/' return '' AFAICS it doesn't break anything in Zope itself and that change would allow to map folderish objects to a file instead of a directory by setting __dav_collection__ to False. Any objections? Cheers, Yuppie ___ 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] Re: zope.app stitching
Philipp von Weitershausen wrote: Jim Fulton wrote: We need to stitch zope.app into Zope 2 more carefully than we are now. Much of what we are stitching is unreleased in Zope3 and depends on things not stitched nto Zope 2. Among other things, this means that we can't use python2.4 test.py -m. to run all tests without getting test failures. It would be great if someone would sort this out before we do any Zope 2.9 releases. :) Well, from that vague we need to do it more carefully I deduce that you would like to stitch in zope.app like we stitch in zope, i.e. each package individually. Yup -- well, maybe not. See my rambling though exercise below. :) Unfortunately, that will not work equally well because there are several text files at zope.app, more than just the __init__.py: DEPENDENCIES.cfg PACKAGE.cfg PUBLICATION.cfg browser.zcml configure.zcml content_types.py datetimeutils.py decorator.py ftesting.zcml menus.zcml meta.zcml servicenames.py timezones.py At least the Python modules and zpkgutils files will be needed in Zope 2 as well. The real problem is that svn:externals doesn't work on files, just on directories. So, we'd have to manage separate copies of those files. Are you sure we want to get into that? Yes. In the next release cycle, I want to take another look at zope.app. In particular, I think it's time, within the Zope 3 project to revisit the concept of core and drastically reduce the size of zope.app by moving things out. This will have one of 2 possible outcomes for Zope 2: - Zope 2 will no longer need to stitch zope.app at all. Everything it needs will be available in individual zope packages, or - zope.app will become small and have only what is needed and Zope 2 will be able to stitch all of it. I'm not sure which it will be, but I suspect the former. In the mean time, meaning for Zope 2.9 only, I think we should just copy the files we need, possibly editing them. Also, in selecting which subpackages from app to include, I suggest starting with what was included in X3.0. Even this might prove to be painful because of our decision to use optional subpackages. For example, many packages have subpackages that provide optional features like index or fssync integration. This means that Zope 2 can't get these via externals without also getting the optional bits. Personally, I don't like optional subpackages and would rather have a much shallower and broader package structure. Another option would be to stop using externals and switch to a build-out model. With a build-out model, you don't rely on a simple checkout to get you all you need. Rather, you run a program of some kind that gets you what you need. This has the advantage that the program can have logic to adjust what you get according to special needs. For example, we are in the process of contributing a build-out framework that Benji built for us here at zc: http://svn.zope.org/Sandbox/zc/buildout/trunk/ Unfortunately, this is lacking docs and tests. :( Alternatively, we could, for Zope 2, as we have for Zope 3, abandon the assumption that everything in the repository is included in the release. I guess now that we are using zpkg, we can arrange that the Zope 2 release includes only stuff in zope and zope.app that we want. In fact, we can probably just reuse the release information from Zope 3.2. OK, so, if we are going to use zpkg to make the release -- and this raises a number of issues too, which I'll brong up in a separate note -- then we can separate repository management from release management and use zpkg facilities to control what we get. In this case, we should really stitch more of Zope 3 into the Zope 2 repository until we get to the point that all of the zope.app tests pass, and we can stitch all of zope.app as we are doing now. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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 )
Get rid of configure/make? (was Re: [Zope-dev] Re: SVN: Zope/trunk/ Merge philikon-zope32-integration branch. Basically, this branch entails:)
Philipp von Weitershausen wrote: Jim Fulton wrote: What changes are those? A fresh Zope trunk checkout works for me. Here's what I did: $ svn co svn+ssh://[EMAIL PROTECTED]/repos/main/Zope/trunk Zope-trunk $ cd Zope-trunk $ ./configure $ make That worked for me (though I usually don't do the configure; make dance, but just do an in-place build with python setup.py build -i; see also below). You used to have to use make instance or make inplace to run the tests. These make commands no longer work. make inplace could probably be fixed by making it an alias for make build, since builds now seem to be in place. Good idea. And I didn't manage to install Zope trunk to a different location. That seems to be completely screwed up. Not supported anymore is the right wording here. Basically, the configure; make; make install dance is going to go away for an SVN checkout. A simple Makefile as we have it in Zope 3 that simply provides shortcuts for in-place builds will probably replace it. I don't think that you or I have the authority to decide this. You're quite right, I don't. I don't know what made me write this in indicative. Sorry for that. When Fred and I brainstormed about which implications a zpkg-based build for Zope 2 had, not being able to install out-of-place was one. Therefore the above paragraph should rather be read as a fact description, not an edict. IOW, rather than saying we're not going to support it anymore, I should really have said that the *current setup* doesn't support it which doesn't mean we can't bring it back. We're not even sure if the configure dance makes sense for a release tarball. The only benefit of the ./configure script is that it (presumably) chooses the right Python for you, which isn't always what you want, anyways. At least I do ./configure --with-python=... more than half of the times. So I could just call python setup.py install with whatever Python I want in the first place. It also lets you specify an install prefix. python setup.py install --home=prefix let's you do that too. More importantly, it is a familiar model for unix systems. True. It is an unfamiliar model for Python software, though. Anyways, I don't think the ./configure script is the issue right now and I certainly don't feel strongly about it. Most people who download Zope 2 are not Python programmers. Many of them become Python programmers later. I think this is a big part of Zope 2's value proposition that we haven't matched in Zope 3 yet. Having said that, I don't really like the configure/make farce myself. I'd be happy to get rid of it. I'm also happy to defer to the vocal majority. Maybe it's worth revisiting this, which is why the provocative subject. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] File uploading with Zope
On 4 Nov 2005, at 02:42, Thanh Hải, Hà wrote: 2005/11/3, Jens Vagelpohl [EMAIL PROTECTED]: No it is not. And doing that opens up security risks. You need to write a Python product or external method. jens Is there an example of how to implement it in external method or python product? I don't know, sorry. jens ___ 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] buildbot failure in Zope trunk 2.4 Windows 2000 zc-buildbot
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '': Build Source Stamp: None Blamelist: BUILD FAILED: failed compile sincerely, -The Buildbot ___ 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] buildbot failure in Zope trunk 2.4 Windows 2000 fred-win
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 fred-win. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '': Build Source Stamp: None Blamelist: BUILD FAILED: failed test sincerely, -The Buildbot ___ 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] buildbot failure in Zope trunk 2.4 Windows 2000 fred-win
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 fred-win. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '': Build Source Stamp: None Blamelist: BUILD FAILED: failed failed slave lost sincerely, -The Buildbot ___ 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] File uploading with Zope
2005/11/3, Jens Vagelpohl [EMAIL PROTECTED]: No it is not. And doing that opens up security risks. You need towrite a Python product or external method.jens Is there an example of how to implement it in external method or python product? ___ 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] Issues with pyperl: perl2.so not found
On 11/3/05, Cameron Beattie [EMAIL PROTECTED] wrote: I'm very happy with Zope and python. Unfortunately my bank doesn't have a python version of it's API which is why I'm trying to use perl with Zope. If you get PyPerl to run, you could probably make a thin layer of python wrapings, and not have to use Zope-perl. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] manage_minimize
Hi,
Zope-2-7-6
I would like to minimize cache of my ZODB
mounteddatabaseby manage_minimize function from PythonScript placed
inRoot Folder.
Icreatedthemounted database
called "mounted_database" in ZODB.
When I do it this way context.Control_Panel.Database.mounted_database.manage_minimize()
it minimizes maindatabase butnot mounted_database,
but when I do it this
waycontext.REQUEST.RESPONSE.redirect('Control_Panel/Database/mounted_database/manage_minimize')
it works.
Why??? I have to use thefirst solution
becouse I'm going to place more code after minimizing.
Regards
Krzychu
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] manage_minimize
On 4 Nov 2005, at 11:33, Krzysztof Kubacki wrote: Hi, Zope-2-7-6 I would like to minimize cache of my ZODB mounted database by manage_minimize function from PythonScript placed in Root Folder. Why? Do you expect to reduce the Zope memory footprint? That won't happen on most operating systems... jens ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] manage_minimize
Am Freitag, 4. November 2005 11:33 schrieb Krzysztof Kubacki:
When I do it this way
context.Control_Panel.Database.mounted_database.manage_minimize() it
minimizes main database but not mounted_database,
but when I do it this way
context.REQUEST.RESPONSE.redirect('Control_Panel/Database/mounted_database/
manage_minimize') it works.
Why??? I have to use the first solution becouse I'm going to place more
code after minimizing.
I believe something like
container.Control_Panel.Database['mounted_storage'].manage_minimize()
should to the trick; and would think that your version should throw an
AttributeError. strange that it doesn't :-)
Hope it helps,
Sascha
--
Gallileus - the power of knowledge
Gallileus GmbH http://www.gallileus.info/
Pintschstraße 16 fon +49-(0)30-41 93 43 43
10249 Berlin fax +49-(0)30-41 93 43 45
Germany
+++
AKTUELLER HINWEIS (November 2005)
Lesen Sie bei Gallileus über aktuelle Forschungsergebnisse
aus den Hochschulen:
http://www.gallileus.info/gallileusnews/gInstitutionen/
+++
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] manage_minimize
Am Freitag, 4. November 2005 11:34 schrieb Jens Vagelpohl: Zope-2-7-6 I would like to minimize cache of my ZODB mounted database by manage_minimize function from PythonScript placed in Root Folder. Why? Do you expect to reduce the Zope memory footprint? That won't happen on most operating systems... you might not get memory back, but you could prevent that too much is consumed in the first place. at least thats what I believe to have observed for long running maintenance jobs that touch many (several thousands) objects during a transaction. of course, if its possible to commit() once in a while saves way more memory. Cheers, Sascha -- Gallileus - the power of knowledge Gallileus GmbH http://www.gallileus.info/ Pintschstraße 16 fon +49-(0)30-41 93 43 43 10249 Berlin fax +49-(0)30-41 93 43 45 Germany +++ AKTUELLER HINWEIS (November 2005) Lesen Sie bei Gallileus über aktuelle Forschungsergebnisse aus den Hochschulen: http://www.gallileus.info/gallileusnews/gInstitutionen/ +++ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] sql access style
I'm about to create a Zope (Plone, in fact) application, as a Package, that will operate on data accessible via SQL (Firebird RDBMS). I'm ordered the data must stay in SQL storage, not in ZODB. Recently I found, outside of Zope, that using python-kinterbasdb module is very straighforward and easy. It's simply about writing SQL statements to Python code. Until then I thought I'll use usual ZSQL Methods for each SQL statement in the application, but kinterbasdb seems to allow a quickier developing. First thing that arises is that I will need to keep the persistent connection reference in the product instance, but it's bearable IMHO. I'm unexperienced in this, please may I hear pros/cons of each method? Thanks in advance. -- \//\/\ (Sometimes credited as 1494 F8DD 6379 4CD7 E7E3 1FC9 D750 4243 1F05 9424.) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] manage_minimize
On 4 Nov 2005, at 12:43, Sascha Ottolski wrote: Am Freitag, 4. November 2005 11:34 schrieb Jens Vagelpohl: Zope-2-7-6 I would like to minimize cache of my ZODB mounted database by manage_minimize function from PythonScript placed in Root Folder. Why? Do you expect to reduce the Zope memory footprint? That won't happen on most operating systems... you might not get memory back, but you could prevent that too much is consumed in the first place. at least thats what I believe to have observed for long running maintenance jobs that touch many (several thousands) objects during a transaction. of course, if its possible to commit() once in a while saves way more memory. It's not only possible to commit once in a while during such jobs, it's what you *should* do. jens ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] manage_minimize
Jens Vagelpohl wrote: It's not only possible to commit once in a while during such jobs, it's what you *should* do. *cough* Stepper *cough* Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] VIRTUAL_URL Failure
Hi, On my Plone site, in CookieCrumbler.py, VIRTUAL_URL is not found in the request variable even though I have a Virtual Host Monster. This means that when logging in, the came_from URL that my site directs to becomes something ugly like http://my.domain.org/VirtualHostBase/http/my.domain.org:80/contentPages This doesn't seem to be an Apache rewriting issue. Should VIRTUAL_URL be found in the request variable and giving the right URL (http://my.domain.org/contentPages), and why isn't it showing up? Peace, George ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] VHM and SSL protection problem
Hello Everyone. I have an existing Cosign-protected site and now I need a site that is only SSL encrypted. We have many apps for which users should be authenticated against a local MySQL database *instead* of Cosign, but we want network traffic to be encrypted. I originally tried setting this up all in one Zope server in different folders, but I can't get SSL to work without Cosign authentication on that Zope server. So I tried installing a separate Zope, as shown below. My current setup is: Macintosh OS X Server 10.4.2, Apache 1.3.33, mod_fastcgi 2.4.2, mod_ssl 2.8.22, OpenSSL 0.9.7g, with Cosign. I have but one ethernet address for the server. Installation #1: Plone 2/Zope 2.7.1 This is our Cosign-protected, stable setup using FastCGI to put Apache in front of Zope (which I know is outdated but I cannot immediately change). Installation #2: Plone 2.1/Zope 2.7.7 I'm trying to use VHM and an Apache rewrite rule to protect this site with SSL. I'm using instructions from http://plone.org/documentation/how-to/apache-ssl . Step number 7 shows this rewrite rule: RewriteRule ^/(.*) http://localhost:8080/VirtualHostBase/https/www.yourmachinename.com:443/$1 So if my original Zope site was http://www.sg.com:8080/ the above rule should simply rewrite the URL to https://www.sg.com:443/ which would force all requests for the http site to go through SSL before being forwarded to Zope. Correct? However, when I create a VHM (without any special mappings) and add the rewrite rule and restart, Apache seems to completely ignore the rewrite. Modifying it in various ways causes errors. Any hints are much appreciated. Thanks! -- SG __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] sql access style
Vlada Macek wrote: I'm about to create a Zope (Plone, in fact) application, as a Package, that will operate on data accessible via SQL (Firebird RDBMS). I'm ordered the data must stay in SQL storage, not in ZODB. Recently I found, outside of Zope, that using python-kinterbasdb module is very straighforward and easy. It's simply about writing SQL statements to Python code. Until then I thought I'll use usual ZSQL Methods for each SQL statement in the application, but kinterbasdb seems to allow a quickier developing. First thing that arises is that I will need to keep the persistent connection reference in the product instance, but it's bearable IMHO. I'm unexperienced in this, please may I hear pros/cons of each method? You might look at ExtZSQL:http://www.zope.org/Members/jccooper/extzsql It is made for using RDBMS in Zope products. --jcc -- Building Websites with Plone http://plonebook.packtpub.com ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
