the commit is finished. Other people
seem to have the same issue, the last checkin mail to the list was sent
2013-09-17.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts
in
Zope?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org
Hanno Schlichting wrote:
On Tue, Jul 10, 2012 at 7:29 AM, yuppie y.2...@wcm-solutions.de wrote:
Zope 2 has customized implementations of the ``browser:view`` and
``browser:page`` directives. I tried to make that code more similar to
zope.browserpage without breaking Zope 2 and CMF. I guess
.
Please let me know if you have any questions or if I did break something.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists
Charlie Clark wrote:
Am 10.07.2012, 16:29 Uhr, schrieb yuppie y.2...@wcm-solutions.de:
I guess the biggest
change I made was removing the Five version of BrowserView from the
base classes.
Please let me know if you have any questions or if I did break
something.
I'm sure that's going
://svn.zope.org/zopetoolkit/branches/1.0/ztk.cfg?rev=123141view=auto
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org
where ever needed. The first part is easy, the second part
a lot of work for many people.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related
2.13.10 are affected?
They are affected. 2.13.6 seems to be a typo. But AFAICT Plone is not
affected because it doesn't use the default user folder implementation
shipped with Zope.
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https
and scope of Zope 2. Maybe at some point this should get
a different name ;-)
I don't want to discuss names, but I think the next release from Zope
trunk should be explicitly a new *major* release.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope
of reverting my change I propose to make auto-checkout in
development.cfg an explicit list of all tested packages instead of using
a wildcard. Or to decide explicitly that we want to test the ZTK against
checkouts of its dependencies.
Any opinions?
Cheers,
Yuppie
://zope3.pov.lt/trac/changeset?new=121748%40zopetoolkit%2Ftrunkold=121746%40zopetoolkit%2Ftrunk
Oops! My mistake. Hope this is fixed now:
http://svn.zope.org/?rev=121787view=rev
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https
them.
Any opinions?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
zope.publisher? I don't use zope.publisher, but I think it
should always use 'utf-8' instead of trying to be smart.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
in
Products.PageTemplates.unicodeconflictresolver.PreferredCharsetResolver.
I'm not going to start that discussion again.
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists
() if the object implements
zope.publisher.interfaces.browser.IBrowserPage.
If there are no objections I'll implement it that way on Zope trunk.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope
the changes can be merged back to Zope?
Does that make sense? I guess that kind of change should only be made on
the trunk.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman
if no Accept-Charset header is set.
And Five always used this line which has the same effect::
charsets = envadapter.getPreferredCharsets() or ['utf-8']
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman
need more site specific stuff than just a profile, so I can't
see a big win.
Anyway: +1 for making the ZCML directive work if package is None
BTW: GenericSetup related questions are generally discussed on the
Zope-CMF list.
Cheers,
Yuppie
. This no longer works:
/usr/local/python2.6/bin/python ./bin/test --all
Should now be:
/usr/local/python2.6/bin/python -S ./bin/test --all
or just:
./bin/test --all
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org
:
install_requires=[
'Zope2 [zope212_compat] = 2.12.15',
]
If Products drop Zope 2.12 support, they can switch to this:
install_requires=[
'Zope2 = 2.13.0',
'Products.MailHost', # required Products
]
Cheers,
Yuppie
___
Zope
time and Zope 2.12 is the primary platform for CMF 2.2. So if you really
want stop maintaining Zope 2.12 soon: Wouldn't it be better to release
CMF 2.3 in time for Plone 4.1?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https
?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman
in the first category.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https
install_requires should specify the new requirement explicitly.
BTW: I just fixed some failing tests on Windows. Hope that doesn't mask
any real issues.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo
that the Interfaces tab of Page Templates
is broken.
I guess this is a Page Template specific traversal issue and could be fixed.
+1.0 for fixing the tab
+0.2 for removing the tab if nobody wants to fix it
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev
?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman
specific files?
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https
, but that doesn't work in CMF.buildout
because it already uses that option.
So I tried to execute the module and noticed that's currently broken.
The -s option doesn't allow to run a specific module.
And if I use the -t option (-ttest_tool), most tests fail :(
Cheers,
Yuppie
=97view=rev
And I hope together with the change in HTTPResponse your issue is
resolved now:
http://svn.zope.org/?rev=99view=rev
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
know if the attached patch fixes the issue.
Cheers,
Yuppie
Index: public/src/zExceptions/unauthorized.py
===
--- public/src/zExceptions/unauthorized.py (revision 62)
+++ public/src/zExceptions/unauthorized.py
,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Hi!
Wichert Akkerman wrote:
On 4/20/10 15:17 , yuppie wrote:
Wichert Akkerman wrote:
I added an extra change (see diff below) to fix that, after which things
seemed to work.
Great!
Can you commit that change along with your other changes?
Yes. I'll write some more tests and commit
discussed in comments #15ff of
https://bugs.launchpad.net/zope2/+bug/372632
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https
Hi again!
yuppie wrote:
Wichert Akkerman wrote:
v is the html as generated by my view. Reraising the exception transfers
control to the bare except in
ZPublisher.Publish.publish_module_standard, which generates the standard
site error page and returns that.
I would have expected
make sure docs and code don't get out of sync? Do we have to
run unittests *and* build the docs before each checkin? Will someone
make sure buildbots and nightly tests report broken docs as well?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope
Hi!
Tres Seaver wrote:
yuppie wrote:
yuppie wrote:
In Zope 2.10 'raise_standardErrorMessage', 'zpublisher_exception_hook'
and therefore 'Publish.publish' did always (re-)raise errors after
rendering. That made sure 'HTTPResponse.exception' was called and
CookieCrumbler was able to hook
yuppie wrote:
In Zope 2.10 'raise_standardErrorMessage', 'zpublisher_exception_hook'
and therefore 'Publish.publish' did always (re-)raise errors after
rendering. That made sure 'HTTPResponse.exception' was called and
CookieCrumbler was able to hook into 'HTTPResponse._unauthorized'.
I'm now
comments are welcome.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https
it removes the sentence All
Rights Reserved. partially or completely.
So depending on a layout difference (line break or not) it produces
copyright headers with different content.
Doesn't make any sense to me, but the people I already asked don't care.
Cheers,
Yuppie
Hi!
Tres Seaver wrote:
yuppie wrote:
Tres Seaver wrote:
So depending on a layout difference (line break or not) it produces
copyright headers with different content.
Doesn't make any sense to me, but the people I already asked don't care.
The All Rights Reserved is a little senseless
? Is
Zope2 in any way useful for non-developers? Is pure TTW development the
best way to get started? Or do you recommend virtualenv as well for
small file-system based projects?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https
pas.
I consider the self-contained scenario still as experimental. Following
the instructions requires much more typing than the other scenarios. But
I'm optimistic it can and will be improved.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope
Hi Chris!
Chris Withers wrote:
yuppie wrote:
I consider the self-contained scenario still as experimental.
You might, I don't. I've deployed this happily in production with a few
customer now.
Just because you don't happen to like it yourself, please don't belittle
it...
I didn't mean
.
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman
.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org
,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman
Hi!
Hanno Schlichting wrote:
On Sun, Dec 27, 2009 at 5:43 PM, yuppie y.2...@wcm-solutions.de wrote:
Why not following the normal procedure? At some point in the past we
decided to add formlib support to Zope 2. That's a commitment. We should
not drop features just like that.
I think
Christian Zagrodnick wrote:
On 2009-12-01 16:36:50 +0100, yuppie y.2...@wcm-solutions.de said:
Christian Zagrodnick wrote:
AttributeError: 'NoneType' object has no attribute 'location'
Should be fixed now. Yuppie
Thanks! And it was such an easy fix! :)
Well. Actually I didn't test
/testing.py,
line 464, in install
if dist.location.endswith('.egg'):
AttributeError: 'NoneType' object has no attribute 'location'
Should be fixed now. Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
Hi!
Chris Withers wrote:
yuppie wrote:
I hope Chris W. will fix this.
I'll try and have a look before Nov 1st.
Great!
He is more familiar with the zopectl code
and he already fixed some other regressions caused by his refactoring.
I have? News to me...
I don't want to argue about
Hi!
Andreas Jung wrote:
Am 26.10.09 22:28, schrieb yuppie:
Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
I'd like to nominate this bug:
https://bugs.launchpad.net/zope2/+bug/461446
You're going to fix it?
I hope Chris W
Hi Chris!
Chris Withers wrote:
(updating myself much much later)
(replying much much later)
Chris Withers wrote:
yuppie wrote:
You ripped my sentence out of context. We were talking about Zope
2.12. And Zope 2.12 currently doesn't use buildout for setting up
instances.
Sure it does
Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
I'd like to nominate this bug:
https://bugs.launchpad.net/zope2/+bug/461446
It's a regression.
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev
what code in Zope2 expects the ZopeVocabularyRegistry to be
registered. Can you remember what needed it?
A wrong import in CMFCalendar did mask the problem, but I just fixed
that and now you can see some CMF tests failing if that import is
removed in Five.
Cheers,
Yuppie
Hi Chris!
Chris Withers wrote:
yuppie wrote:
yuppie wrote:
Currently buildout is just used to set up the software.
Wrong. The buildout I posted, which uses no fancy recipes, sets up an
instance. The egg cache, as such, is the software...
You ripped my sentence out of context. We were
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Currently buildout is just used to set up the software.
Wrong. The buildout I posted, which uses no fancy recipes, sets up an
instance. The egg cache, as such, is the software...
You ripped my sentence out of context. We were talking about
Hi Chris!
Chris Withers wrote:
yuppie wrote:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
I wish we could just bless buildout as the way to set up Zope 2.12,
then mkzopeinstance becomes moot.
Not everybody agrees with that. But nevertheless, both
Hi Chris!
Chris Withers wrote:
yuppie wrote:
SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
somewhere on sys.path.
So this no longer works in zopectl:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
I wish we could just bless
Andreas Jung wrote:
On 23.07.09 12:10, yuppie wrote:
Any thoughts? Is the 2.12 branch still open for changes like that?
Go ahead. I also had to fix a similar issue some days ago inside
Zope startup code.
Done.
http://svn.zope.org/?rev=102230view=rev
http://svn.zope.org/?rev=102231view=rev
that?
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
' is found
but not the right place to split the path.
I'm fine with that. I can test the changes with the project
which I used as base when I wrote the path cleanup code.
I checked in that change. Can you please test?
Thanks! Yuppie
___
Zope-Dev
py_strings, zcml_strings and tal_strings in
functions that implement the new interface? This would make it possible
to add them to the makers list and call them in the same loop.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http
see a way to unify that in a backwards
compatible way. That's why I proposed to wrap them in new
z3c.recipe.i18n specific functions.
I propose I start with the changes I have in mind. Of course you can
improve that further after I'm done.
Cheers, Yuppie
to split the path.
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
arguments and fall back to the old
signature for BBB.
Does all that make sense? Any objections or better ideas?
Should changes for POTMaker go into zope.app.locales.extract or should
z3c.recipe.i18n use a customized version?
Cheers,
Yuppie
,
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 )
Hi Andreas!
Andreas Jung wrote:
On 29.06.09 12:48, yuppie wrote:
3.) remove security declarations from ZCTextIndex and DateRangeIndex
All the other indexes don't have security declarations. AFAICS there is
no way to access indexes from untrusted code without having the 'Manage
short:
This is only the case if the context of the view is also a view. In all
other cases they still work.
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
Tres Seaver wrote:
As I said earlier: five.localsitemanager should just be made part of
the Zope2 trunk: it is tightly-coupled to Zope2, and its presence as a
separate pacakge is just confusing and error-prone.
+1
___
Zope-Dev maillist -
in
App.class_init instead of using from App.class_init import
default__class_init__ as InitializeClass everywhere?
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
in a different context. If we group changes on the trunk the same way as
on the current maintenance branch, the context will always be the same.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman
Jens Vagelpohl wrote:
On Jun 19, 2008, at 12:32 , yuppie wrote:
There is always *one* well defined current maintenance branch. Version
numbering *does* imply a time line if you ignore old maintenance
branches. It's not hard at all to get this right.
I don't think that assumption holds true
Jens Vagelpohl wrote:
On Jun 19, 2008, at 13:36 , yuppie wrote:
Jens Vagelpohl wrote:
On Jun 19, 2008, at 12:32 , yuppie wrote:
There is always *one* well defined current maintenance branch.
Version numbering *does* imply a time line if you ignore old
maintenance branches. It's not hard
the branch to
the trunk. No big burden for the maintainers, but a big win for the users.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related
Jens Vagelpohl wrote:
On Jun 18, 2008, at 19:00 , yuppie wrote:
Why do we maintain a CHANGES.txt file? Who reads it and why?
The audience I have in mind are users of released versions. They read
CHANGES.txt to figure out what's new in a release.
Let's take Zope 2 as an example:
Most
Hi!
Jens Vagelpohl wrote:
On Jun 18, 2008, at 19:27 , yuppie wrote:
That's not the only audience. I as a developer consult CHANGES.txt to
(hopefully) find *all* changes on the respective branch or on the
trunk that have flowed into it until now.
Can't developers use the subversion history
,
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 )
.
Maybe we don't need a strict policy for this, but some guidance would be
nice to have.
Any opinions? Any guidelines I missed?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
packages instead. The AdvancedQuery code
might become part of the ZCatalog package, ManagableIndex might be
converted to a non-products package.
Of course this is just my opinion. These are no official rules.
Cheers,
Yuppie
___
Zope-Dev
this changes the behavior.
If there are no objections, I'll resolve these two issues on the Zope trunk.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
Hi!
Philipp von Weitershausen wrote:
yuppie wrote:
The Zope 2.10 branch still uses Five 1.5.1. There are a few changes on
the Five 1.5 branch (including a security fix) which should become
part of Zope 2.10.2.
I volunteer to resolve this as follows:
Five releases are now linked tightly
?
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
Hi!
Andreas Jung wrote:
--On 29. Oktober 2006 10:06:42 +0100 yuppie [EMAIL PROTECTED]
wrote:
Oops! Sorry! I did not mean to cause any confusion:
- AFAICT the 2.10 branch points already to the 3.3.0 tag.
Right.
However Philipp pointed out that the Zope 2 trunk uses the Zope 3 trunk
.
The failure showed up after this checkin:
http://svn.zope.org/?rev=70383view=rev
But I didn't have time to track it down, so I opened this collector
issue: http://www.zope.org/Collectors/Zope/2198
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
Hi Chris!
Chris Withers wrote:
yuppie wrote:
# Support old-style product metadata. Older products may
# define attributes to name their permissions, meta_types,
# constructors, etc.
[followed by the code that interprets the 'methods' attribute]
So 'methods' is BBB code
Hi Chris!
Chris Withers wrote:
yuppie wrote:
I believe the Hippocratic Oath should be followed in subjective cases
like this. First, do no harm.
Cruft does harm. It discourages people who want to understand and
improve Zope. And it encourages people to stick to bad coding habits.
As far
.
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
with extending the deprecation period by one more release cycle.
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
Hi Chris!
Chris McDonough wrote:
On Jun 14, 2006, at 1:00 PM, yuppie wrote:
It's not that simple. registerClass has an optional 'legacy' argument
that does something quite similar. It just monkey patches
ObjectManager instead of Folder. So at least for some use cases
registerClass
']))
File /usr/local/lib/Zope-2.10/lib/python/OFS/Traversable.py, line
263, in un
restrictedTraverse
obj = next
UnboundLocalError: local variable 'next' referenced before assignment
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
and
doesn't provide any benefits.
Just my 2 cents.
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
for that feature release as soon as necessary
(rooted at the trunk right before the first non-bugfix checked in).
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
Hi!
Tres Seaver wrote:
yuppie wrote:
Tres Seaver wrote:
- CMFDefault/skin/configure.zcml blows up because the syntax of the
'browser:skin' directive has changed in a BBB-incompatible
way. The
now-failing directive is::
browser:skin
name=cmf
layers=cmf default
Tres Seaver wrote:
yuppie wrote:
Who made up that policy? And why?
I don't think it's a good policy. It is very unlikely that people want
to mess up the trunk right after the first beta. I'd prefer a policy
like that::
After the first beta of the new feature release is made, we
create
, but patch_listDefaultTypeInformation seems to require
listDefaultTypeInformation)
3.) registerPackage works out of the box with Five 1.4 / Zope 2.10
(also not tested)
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo
and
zope.app.locales.extract isn't really made for reuse. But it contains
some useful code.
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
Hi Philipp!
Philipp von Weitershausen wrote:
yuppie wrote:
And CMF uses zope.app.locales.extract. Not in the CMF products, but for
a script that extracts i18n messages. That script is a quick hack and
zope.app.locales.extract isn't really made for reuse. But it contains
some useful code
Philipp von Weitershausen wrote:
yuppie wrote:
Sounds good to me. At least if someone finds time to refactor the
extractor. For now it is quite specific code for creating the zope
gettext files and would better fit in zope.translations.
On second thought, I think we should think about
1 - 100 of 209 matches
Mail list logo
