l 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 pos
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
ay five.formlib uses it should work with both
versions. So I would fall back to ``makeClassForTemplate`` if import of
``SimpleViewClass`` doesn't work.
HTH,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailm
Hanno Schlichting wrote:
On Tue, Jul 10, 2012 at 7:29 AM, yuppie 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 the biggest change
I made
Charlie Clark wrote:
Am 10.07.2012, 16:29 Uhr, schrieb yuppie :
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 to break any cod
.
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
[sources] section including comment:
http://svn.zope.org/zopetoolkit/branches/1.0/ztk.cfg?rev=123141&view=auto
Cheers, Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
ne in Zope 4 and to add explicit security
declarations 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/zop
are not vulnerable.
>
> Can you confirm whether or not Zope 2.13.6 through 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
___
7;m outlining here has of course almost nothing to do with the
> original idea 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,
d 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
___
and
> buildbot does not remove "ssh+" from source urls in those files.
>
> [1]
> http://zope3.pov.lt/trac/changeset?new=121748%40zopetoolkit%2Ftrunk&old=121746%40zopetoolkit%2Ftrunk
>
Oops! My mistake. Hope this is fixed now:
http://svn.zope.org/?rev=121787&view=rev
ose the naive marker is preserved, but not the time zone:
>>> dt = DateTime('2011/03/09 11:00:00')
>>> dt.timezoneNaive()
True
>>> dt.timezone()
'GMT+1'
I would argue the people who don't care about naive or not should set
objections, I'll implement it that way in ZPublisher.
What about 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-De
stProcessInputs() 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.
Charlie Clark wrote:
> Am 04.03.2011, 08:58 Uhr, schrieb yuppie:
>
>> If we always send UTF-8, their current implementation doesn't make much
>> sense to me. Don't know if we really should try to fall back to all the
>> charsets mentioned in Accept-Charset. But
Hi!
Laurence Rowe wrote:
> On 2 March 2011 11:29, yuppie wrote:
>> Laurence Rowe wrote:
>>> On 2 March 2011 10:00, yuppiewrote:
>>>> Martin Aspeli wrote:
>>>>> I don't know what setPageEncoding() does, though.
>>>>
>
Hi Charlie!
Charlie Clark wrote:
> Am 02.03.2011, 12:29 Uhr, schrieb yuppie:
>
>> getPreferredCharsets()[0] always returns 'utf-8' **if** UTF-8 is
>> accepted.
>
>> If 'utf-8' is not in getPreferredCharsets(), it is not very likely that
>> the
Laurence Rowe wrote:
> On 2 March 2011 10:00, yuppie wrote:
>> Martin Aspeli wrote:
>>> I don't know what setPageEncoding() does, though.
>>
>> It sets a response Content-Type header with the first charset
>> processInputs tries for decoding.
>
>
() does, though.
It sets a response Content-Type header with the first charset
processInputs tries for decoding.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTM
ons. Maybe 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-
't want to create a Python package just so
> I can save a couple settings in my (Plone) site.
Usually I 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: Gen
e how to diagnose
> remotely.
Zope 2 trunk now uses the latest testrunner version. 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
Hi!
Hanno Schlichting wrote:
> On Tue, Jan 4, 2011 at 2:53 PM, yuppie wrote:
>> Using CMF 2.2 for Plone 4.1 means we have to maintain CMF 2.2 for a long
>> time and Zope 2.12 is the primary platform for CMF 2.2. So if you really
>> want stop maintaining Zope 2.12 soon: Wou
have to maintain CMF 2.2 for a long
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
Managers',
],
That would make it possible to specify the Zope2 dependency this way:
install_requires=[
'Zope2 [zope212_compat] >= 2.12.15',
]
If Products drop Zope 2.12 support, they can switch to this:
install_requires=
es noise on the list and makes it hard to recognize
failures 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
te is not clear about that and maybe
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-D
I can confirm 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
_
from the way tests are filtered:
The -m filter is applied *before* test modules are imported.
The -t filter is applied *after* importing all available test modules.
Some nasty code in Zope 2 behaves differently if different modules are
imported before running the tests.
Che
Hi!
Hanno Schlichting wrote:
> On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspeli
> wrote:
>> On 29 July 2010 20:14, yuppie wrote:
>>> Sure. But do you always run all tests it picks up while working on a
>>> specific test file? Or do you use bin/test with options
Hi Martin!
Martin Aspeli wrote:
> On 29 July 2010 20:14, yuppie wrote:
>> Martin Aspeli wrote:
>>> I never do either. I install zc.recipe.testrunner in a buildout and
>>> use bin/test, which picks up tests in modules automatically.
>>
>> Sure. But do you
low to
run 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
there a better solution for using zope testrunner than the one
shown above?
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!
Christian Theune wrote:
> On 04/09/2010 05:31 PM, yuppie wrote:
>> Tres Seaver wrote:
>>> yuppie wrote:
>>>> Tres Seaver wrote:
>>>> So depending on a layout difference (line break or not) it produces
>>>> copyright headers with differen
e.org/?rev=97&view=rev
And I hope together with the change in HTTPResponse your issue is
resolved now:
http://svn.zope.org/?rev=99&view=rev
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mail
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 ot
CookieCrumbler and PAS.
A better fix would be to store the rendered exception value in the
response object instead of the exception object. That way we could
re-raise *all* exceptions as it was done in older Zope versions.
But this would have been a bigger
Please let me 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/una
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 ret
remove that code block so we always return the
> result of the view everything works as I would expect.
I tried to fix the bug discussed in comments #15ff of
https://bugs.launchpad.net/zope2/+bug/372632
Cheers,
Yuppie
___
Zope-Dev maillist
+1 in general, but I'm concerned about one thing:
How can we 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
_
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 s
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
> CookieCrumbl
where the errors are currently catched.
2.) Re-raise the original errors. And store the rendered value somewhere
else. Maybe in the response object.
What do you think? Any comments are welcome.
Cheers,
Yuppie
___
Zope-Dev maillist -
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'
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
hy do they want to install and run Zope2? 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-
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 you
heaven help you if you forget
>to configure the index properly!). The second leaves you without
>the annotated config file, a *major* faux pas.
I consider the self-contained scenario still as experimental. Following
the instructions r
there. ZPublisher.TaintedString was definitely the wrong
place.
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!
Hanno Schlichting wrote:
> On Sun, Dec 27, 2009 at 5:43 PM, yuppie 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.
&g
heers,
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/ma
features just like that.
Zope 2.13 can still have the "runs on ZTK" label if it ships with
additional packages.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No
Christian Zagrodnick wrote:
> On 2009-12-01 16:36:50 +0100, yuppie said:
>> Christian Zagrodnick wrote:
>>> AttributeError: 'NoneType' object has no attribute 'location'
>> Should be fixed now. Yuppie
>
> Thanks! And it was such an easy fix! :)
test)
> File
> "/Users/zagy/development/eggs/zc.buildout-1.4.2-py2.6.egg/zc/buildout/testing.py",
>
> line 464, in install
> if dist.location.endswith('.egg'):
> AttributeError: 'NoneType' object has no attribute 'location'
Shoul
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 h
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:
>>
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-De
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 cur
pe starts. I
> don't know 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
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 "th
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
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 wa
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&
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=102230&view=rev
http://svn.zope.o
sed to execute runzope or zopectl.
- uses cases might exist that no longer work after that change
Any thoughts? Is the 2.12 branch still open for changes like that?
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope.org
http://ma
v
Do you want to improve that further or do you propose to modify
py_strings, zcml_strings and tal_strings? They all have currently
different signatures. I can't 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 f
makers
>> -
>>
>> Proposal: Pass in the additional arguments and fall back to
>> the old signature for BBB.
Done. I also added site_zcml as argument.
What about wrapping py_strings, zcml_strings and tal_strings in
functions that implement the new interface? Th
seless.
>>
>> The current code doesn't work for me because 'src' 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 wh
h like:
>
> zope/session.py:3
>
> It could be that the if part is working for all usecases.
> but I'n not sure without debugging.
Debugging doesn't help much if we don't know all use cases.
What about testing it like this:
We remove the 'else' part and wait u
exclude_dirs), basePath)
I miss 'domain' and 'include_default_domain'.
Proposal: Pass in the additional arguments and fall back to the old
signature for BBB.
Does all that make sense? Any objections or better ideas?
Should changes
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
ese changes on the 2.12 branch
and the trunk.
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 )
ations. Who
> did that?
Sorry. That checkin message was too 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/mail
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 - Zope-
o add an alias 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
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 ha
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
hat. In the format you propose the change note has to be placed
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 mai
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 subversi
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 exam
ch
2.10 release. You just have to copy that information from 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/
nit__.py?
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 )
ecommended version.
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/l
't that a step in
the wrong direction?
- Should we add new products to the core? I thought we want to move away
from products and use python packages instead. The AdvancedQuery code
might become part of the ZCatalog package, ManagableIndex might be
conv
turns the default value if the value is not true. This changes values
like 0 or False to the default value.
Looks like a bug to me. But fixing this changes the behavior.
If there are no objections, I'll resolve these two issues on the Zope trunk.
Cheers,
Yuppie
___
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
ses.
Thoughts?
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.z
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
t the problem is.
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.
ince May.
The failure showed up after this checkin:
http://svn.zope.org/?rev=70383&view=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-D
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&#
#x27;meta_types'
support, so I guess they can be removed in Zope 2.11.
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 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 ha
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
regi
Hi Chris!
Chris McDonough wrote:
On Wed, 2006-06-14 at 15:42 +0200, yuppie wrote:
Reading the sources I had the impression
that the fact there was no warning for the deprecated feature was a bug
and I did consider my change a bugfix. Without warning it was already
deprecated for many years
ars.
I'm fine 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 list
hods.
As Florent already pointed out using it for general monkey patching
doesn't look like a good idea. We only can improve the product
initialization if we first remove some cruft.
Cheers,
Yuppie
___
Zope-Dev maillist - Zope-Dev@zope
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 mad
1 - 100 of 228 matches
Mail list logo
