> Yes, unless Zope 3 TALES is very unlike Zope 2 TALES. We deliberately
> restricted the syntax of namespaces to be valid variable names in Python
> (and most other languages). This allowed, for example, direct use of
> the name of a namespace as a function in a Python expression:
>
> python:
Sidnei da Silva wrote:
That smells to me like we need a mime-type negotiator or something,
pretty much like we have a language negotiator for deciding which
language to use for translations.
No really, all this thread seems to have really uncovered so far is that
macros in different ZPT modes
There is a problem to build extensions for the Zope3 trunk (and I guess for
ZODB trunk as well) - all extension module names is lowercased now. For example:
gcc -pthread -shared build/temp.linux-i686-2.4/src/persistent/TimeStamp.o -o
src/persistent/timestamp.so
I guess the problem that the
Hi!
I have been scratching my head on this one, there is something
counter-intuitive in the way path adapters are used in ZPT.
If I have a path adapter declared as:
and Displayable:getDisplay takes an optional argument
for a ZPT programmer, it seems natural to write:
tal:define="
displa
Andreas Reuleaux schrieb:
On Thu, Sep 01, 2005 at 06:58:42PM +0200, Tonico Strasser wrote:
...
What's your point?
Well, from reading your conversation with Philipp I got the
impression, that you wanted to say something like
"XML-Mode in PTs respectively XHTML is useless if served with
the wr
Chris Withers schrieb:
For me, the fact that ZPT uses a field called "content_type" to control
the mode is bogus :-(
That content_type value is also used to set the content-type in the
response by default.
Tonico
___
Zope3-dev mailing list
Zope3-
Dmitry Vasiliev wrote:
There is a problem to build extensions for the Zope3 trunk (and I guess
for ZODB trunk as well) - all extension module names is lowercased now.
For example:
gcc -pthread -shared
build/temp.linux-i686-2.4/src/persistent/TimeStamp.o -o
src/persistent/timestamp.so
I g
On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
> There is a problem to build extensions for the Zope3 trunk (and I guess
> for ZODB trunk as well) - all extension module names is lowercased now.
> For example:
This is a symptom of getting the wrong ZConfig version. This setup
requires 2.3.
Fred Drake wrote:
Ugh, the problem is in new setup.py at line 24:
site.addsitedir(buildsupport)
'src' directory now appended at the end of the sys.path and old version of
ZConfig had been imported by zpgsetup.
This is surprising. The sys.path.insert(0, ...) line (which you
removed) was inte
Hi!
I have summarize how the rendering engine in cpsskins in built, from
content, display and format elements to filters, rendering engines:
http://www.z3lab.org/sections/documentation/cpsskins-rendering
with lots of diagrams and explanations. This part of the architecture
has stabilized.
/JM
On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
> Before the fix (rev. 38239):
>
>['buildsupport', ..., 'src']
>
> After the fix:
>
>['src','buildsupport', ...]
Ok, I think I understand this now. Appearantly you have some version
of ZConfig installed elsewhere that is getting pic
Fred Drake wrote:
On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
I now agree that the change is reasonable. It needs a comment that
it's protecting against importing *installed* versions of ZConfig.
It would also be nice if it used .insert() instead of a [:0] slice.
--
Benji York
Senior
Benji York <[EMAIL PROTECTED]> writes:
> Fred Drake wrote:
>> On 9/2/05, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
>> I now agree that the change is reasonable. It needs a comment that
>> it's protecting against importing *installed* versions of ZConfig.
>
> It would also be nice if it used .ins
Ruslan Spivak wrote:
I think Dmitry used that because of slice assignment and i don't see
how it can be done with index assignment of insert():
Indeed! I was thinking of a single item instead of a list. We could
use a loop, but I don't think that's any better. Thanks for the
clarification.
Ok,i get Z3 from trunk and run "make" and "bin/mkzopeinstance". Result:
Traceback (most recent call last):
File "bin/mkzopeinstance", line 45, in ?
sys.exit(main(from_checkout=from_checkout))
File "/home/os/WORK/Z3S
On 9/2/05, Garanin Michael <[EMAIL PROTECTED]> wrote:
> OSError: [Errno 2] No such file or directory:
> '/home/os/WORK/Z3Sandbox/package-includes'
>
> Is it bug?
Ah, yes! This is indeed a bug introduced by some recent changes. I'll fix it.
-Fred
--
Fred L. Drake, Jr.
Zope Corporation
16 matches
Mail list logo
