Log message for revision 40687:
Changed:
U Zope/trunk/doc/CHANGES.txt
-=-
Modified: Zope/trunk/doc/CHANGES.txt
===
--- Zope/trunk/doc/CHANGES.txt 2005-12-11 08:42:50 UTC (rev 40686)
+++ Zope/trunk/doc/CHANGES.txt 2005-12-11
Log message for revision 40688:
updated to latest Z3 trunk
Changed:
_U Zope/trunk/lib/python/zope/
-=-
Property changes on: Zope/trunk/lib/python/zope
___
Name: svn:externals
- app -r 40549
Log message for revision 40690:
updated Z3 trunk
Changed:
_U Zope/branches/ajung-zpt-integration/lib/python/zope/
-=-
Property changes on: Zope/branches/ajung-zpt-integration/lib/python/zope
___
Name: svn:externals
- app
Log message for revision 40691:
cleanup
Changed:
U Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/__init__.py
-=-
Modified:
Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/__init__.py
===
---
Log message for revision 40693:
added
Changed:
A Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/ZPT.py.scary
-=-
Added: Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/ZPT.py.scary
===
---
Log message for revision 40698:
This version is now fully functional and without dependencies from
Products.PageTemplates
Changed:
U Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/ZPT.py
D Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/ZPT.py.scary
-=-
Log message for revision 40700:
added
Changed:
A
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/PageTemplateFile.py
-=-
Added:
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/PageTemplateFile.py
Log message for revision 40701:
removed
Changed:
D
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/PathIterator.py
D
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/PythonExpr.py
-=-
Deleted:
Log message for revision 40703:
cleanup
Changed:
D
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/CHANGES.txt
D
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/examples/
-=-
Deleted:
Log message for revision 40704:
you're time has come, no longer needed for Z3 ZPTs
Changed:
D Zope/branches/ajung-zpt-integration/lib/python/TAL/
-=-
___
Zope-Checkins maillist - Zope-Checkins@zope.org
Log message for revision 40705:
removed
Changed:
D Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/
-=-
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
Log message for revision 40706:
made unittests pass
Changed:
U
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/ZopePageTemplate.py
U
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/pt/ptEdit.pt
U
Log message for revision 40707:
some more comments
Changed:
U
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/PageTemplateFile.py
-=-
Modified:
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/PageTemplateFile.py
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2134
Blamelist: andreasjung,gregweb,jens,oestermeier
BUILD FAILED: failed test
sincerely,
-The Buildbot
Summary of messages to the zope-tests list.
Period Sat Dec 10 12:01:01 2005 UTC to Sun Dec 11 12:01:01 2005 UTC.
There were 8 messages: 8 from Zope Unit Tests.
Test failures
-
Subject: FAILED : Zope-trunk Python-2.4.2 : Linux
From: Zope Unit Tests
Date: Sat Dec 10 22:07:55 EST 2005
(Sorry for X-post)
Hi,
I proposed to clean up the developer zone a bit.
I'll do that without a lot of fuss as I have to goals:
- get information up to date
- reduce the amount of false / out-of-date information
- structure it in small steps so important stuff is found easier
I'll make an
Hi,
I have a working implementation for Zope 3 ZPTs within Zope 2. It is
currently implemented through a new class ZPT which implements the same
functionality as Products.PageTemplates.ZopePageTemplate. I am currently
thinking about the migration to the new implementation. Would it be
Am Sonntag, den 11.12.2005, 13:16 +0100 schrieb Andreas Jung:
Hi,
I have a working implementation for Zope 3 ZPTs within Zope 2. It is
currently implemented through a new class ZPT which implements the same
functionality as Products.PageTemplates.ZopePageTemplate. I am currently
thinking
--On 11. Dezember 2005 13:42:58 +0100 Tino Wildenhain [EMAIL PROTECTED]
wrote:
Are there different object-attributes in both classes?
If not, you could simple replace with the same old
class name.
The Z3 ZPT implementation seems to use the same attrs. So I could just
replace the class
Am Sonntag, den 11.12.2005, 15:03 +0100 schrieb Andreas Jung:
...
The Z3 ZPT implementation seems to use the same attrs. So I could just
replace the class implementation. Some first quick tests show that there is
no further need for a migration..it just works :-)
Lets praise the wonderful
Morten W. Petersen wrote:
Hi,
I'm having some code that bombs out trying to commit a transaction; I
believe it's because of new ways of doing things in Zope 2.9.. how do
you call the equivalents of get_transaction().commit() and abort() in
Zope 2.9? Will those new ways work with Zope
import transaction
transaction.get()
transaction.commit()
transaction.abort()
transaction.savepoint()
This works since 2.8, but not in 2.7. Nearly every project has come
up with its own backward compatibility module though. See for example
CMFCore.utils.transaction or CMFPlone.transaction.
Stefan H. Holek wrote:
import transaction
transaction.get()
transaction.commit()
transaction.abort()
transaction.savepoint()
This works since 2.8, but not in 2.7. Nearly every project has come up
with its own backward compatibility module though. See for example
CMFCore.utils.transaction or
This works since 2.8, but not in 2.7. Nearly every project has come
up with its own backward compatibility module though. See for example
CMFCore.utils.transaction or CMFPlone.transaction.
I'm dispayed to hear this. :( The old use of __builtins__.get_transaction
should be deprecated
--On 11. Dezember 2005 17:01:56 +0100 Morten W. Petersen
[EMAIL PROTECTED] wrote:
Hi,
I'm having some code that bombs out trying to commit a transaction; I
believe it's because of new ways of doing things in Zope 2.9.. how do
you call the equivalents of get_transaction().commit() and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
--On 11. Dezember 2005 17:01:56 +0100 Morten W. Petersen
[EMAIL PROTECTED] wrote:
Hi,
I'm having some code that bombs out trying to commit a transaction; I
believe it's because of new ways of doing things in Zope 2.9..
--On 11. Dezember 2005 12:28:04 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
Stefan H. Holek wrote:
import transaction
transaction.get()
transaction.commit()
transaction.abort()
transaction.savepoint()
This works since 2.8, but not in 2.7. Nearly every project has come up
with its own
A number of ZODB gimmicks were officially deprecated in ZODB 3.4, and
removed in ZODB 3.6. Zope 2.9 uses the latter. From the ZODB NEWS
file for 3.6:
Removal of Features Deprecated in ZODB 3.4
--
(3.6b2) ZODB 3.6 no longer contains features officially
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux
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 test
sincerely,
-The Buildbot
Andreas Jung wrote:
--On 11. Dezember 2005 12:28:04 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
Stefan H. Holek wrote:
import transaction
transaction.get()
transaction.commit()
transaction.abort()
transaction.savepoint()
This works since 2.8, but not in 2.7. Nearly every project has come
[Jim Fulton]
...
BTW, This is a good example for why I want to start using time-based
deprecation.
In a world with time-based releases, is there a difference?
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
Tim Peters wrote:
[Jim Fulton]
...
BTW, This is a good example for why I want to start using time-based
deprecation.
In a world with time-based releases, is there a difference?
Yes, because release numbers aren't very helpful when software
is used by many applications. For example, I
Sorry for redundancy if this is a known problem, but
I just now grabbed the 2.9.0-b1 tarball and noticed this:
[EMAIL PROTECTED] Zope-2.9.0b1 $ ./configure
--prefix=/home/pw/Zope-2.9.0b1-SoftwareHome
Configuring Zope installation
Testing for an acceptable Python interpreter...
Python version
Am Sonntag, den 11.12.2005, 23:19 -0500 schrieb Paul Winkler:
Another quickie problem report - no time to investigate further right
now, but can anybody else reproduce? If so, I'll try to fix tomorrow...
In a fresh 2.9.0-b1 instance, made via bin/mkzopeinstance, I get this
when I click the
Hi all!
I'm slightly burned out and bored with certain areas of Zope 2 Zwiki
development. I think the product will provide some value for a while
yet, and it's not too late to shake things up and make a bigger splash.
If we don't do this during the period of Zwiki Zope 2's
relevance, our
Hi!
Is it at all impossible to use XML-RPC _within_ a ZOPE architecture?
What I mean is:
I have a nested call structure:
1. Python script calls a method from a ZODB object
2. That method calls a Python module function
3. That module function dispatches an XML-RPC call to the same ZODB
object
On Sunday 11 December 2005 22:30, you wrote:
Hi all
Sorry if this is not a specific zope question but I'm confident someone
will be able to help me with the following.
I have an input form on a webpage and below it a table which pulls out of
a database. The column headers in the
This is client side processing (could be done via repetitive calls to the
server, but very inefficient), so you want a javascript-type of solution.
Not a zope solution.
Trying googling 'javascript dynamic lists'... it should get you going in the
right direction.
Jonathan
- Original
Jonathan wrote:
This is client side processing (could be done via repetitive calls to
the server, but very inefficient), so you want a javascript-type of
solution. Not a zope solution.
Trying googling 'javascript dynamic lists'... it should get you going
in the right direction.
Jonathan
David H wrote:
Jonathan wrote:
This is client side processing (could be done via repetitive calls to
the server, but very inefficient), so you want a javascript-type of
solution. Not a zope solution.
Trying googling 'javascript dynamic lists'... it should get you going
in the right
It really *is* in your interests to ensure a single request completes
all your functional requirements ;)
That's not possible unfortunately. The design of the system is rather
complex, and unalterable in this respect. However, it is not true that
it is usually possible to fulfil this
OK, the following is the case:
The setup is for functions dispatching either locally or via XML-RPC.
At the moment, the mechanism I use is to detect locality is flawed and
thus doesn't work well. So I have local XML-RPC calls where I could
have global ones. But.
1. I need that possibility for
42 matches
Mail list logo
