Oh cool! I didn't know :) Thank you.
2009/2/6, Stephan Richter srich...@cosmos.phy.tufts.edu:
On Thursday 05 February 2009, Dan Korostelev wrote:
BTW, it would be great to have that script published so any developer
could use it to set roles for new packages. Stephan? :)
zope.pypisupport
I just committed a new section to zope3docs about migration to newer
Zope 3 releases.
I think we should maintain a list of most important changes that could
break backward-compatibility, like recent changing exception types
used in zope.container in a separate document, so people who are
Hi there,
On Fri, Feb 6, 2009 at 12:10 PM, Dan Korostelev nad...@gmail.com wrote:
[snip]
For ZODB objects I think its okay for now not to use deprecations and
to use the upgrade tool, but for the imports of other things that were
moved elsewhere, I still think we need to bug developers that
Dan Korostelev wrote:
I just committed a new section to zope3docs about migration to newer
Zope 3 releases.
I think we should maintain a list of most important changes that could
break backward-compatibility, like recent changing exception types
used in zope.container in a separate
Dieter Maurer wrote:
Chris Withers wrote at 2009-1-30 18:50 +:
Brian Sutherland wrote:
zope.configuration.x
zope.configuration.y
Please don't, having namespace packages that contain files (as
zope.configuration already does) breaks setuptools.
Then setuptools needs fixing.
But not
Jim Fulton wrote:
zope.configuration isn't a namespace package. It is simply a package
with subpackages.
Does setuptools support something like:
packagea:
packagea/__init__.py
packagea/amodule.py
packagea.something:
packagea/__init__.py
packagea/something/__init__.py
Andreas Jung wrote:
At least I added a patch to buildout at some time ago in order to
make the default timeout configurable through a command-line option
(or was it a buildout options - I can't remember).
Would be good to know where this lives and/or how Christian was limiting
the timeout for
Christian Theune wrote:
It's only a command line option right now.
Which one?
Making it configurable
through a buildout option would be nice too.
Yes, so it can live in default.cfg!
Chris
--
Simplistix - Content Management, Zope Python Consulting
-
Lennart Regebro wrote:
On Thu, Jan 22, 2009 at 10:38, Chris Withers ch...@simplistix.co.uk wrote:
Note that Jim never explained to me how he does these audits, but I gathered
some methods he used in conversations. I think I did a pretty thorough job
during the review.
Yeah, this disturbs me a
Hey Dan and everybody,
I've taken the document Dan started and have reorganized it a bit and
added bits I know of what happened at the sprint last week. I've also
introduced an 'introduction' section which discusses the aim of many of
the changes made and the general response a developer
On Fri, 06 Feb 2009 12:42:37 +
Chris Withers ch...@simplistix.co.uk wrote:
Christian Theune wrote:
It's only a command line option right now.
Which one?
-t
Making it configurable
through a buildout option would be nice too.
Yes, so it can live in default.cfg!
Exactly.
--
On Fri, 06 Feb 2009 12:35:09 +
Chris Withers ch...@simplistix.co.uk wrote:
Jim Fulton wrote:
zope.configuration isn't a namespace package. It is simply a
package with subpackages.
Does setuptools support something like:
packagea:
packagea/__init__.py
packagea/amodule.py
Hi all,
I just ran all tests over night and here is the result
Tests with errors:
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest
Tres Seaver wrote:
Ugh. -1 to any attempt to use space suits in Z2. I would rather move
to a model which made it easy to mark some / all TTW objects as
trusted, disabling security checks altogether: the untrusted users
can edit TTW code use case is pretty much irrelevant for any site I
On Friday 06 February 2009, Martijn Faassen wrote:
True, but one never knows (perhaps some modification to setup.py,
say), and I think we should have a general rule any PyPI package
that's part of the Zope 3 framework (handwave that here for now)
should be owned by a group of people.
Yep,
+- Make ``class`` directive schemas importable from old location,
+ raising a deprecation warning. It was moved in the previous release,
+ but some custom directives could possibly use its schemas.
Out of curiosity, *was* it used by custom directives that you know of?
Well, I personally
Hey,
On Fri, Feb 6, 2009 at 11:32 AM, Dan Korostelev nad...@gmail.com wrote:
[snip]
Okay, reuse of directive definitions and implementations is more
widespread than I thought initially. Which is silly of me, as Grok
itself also reuses directive actions (but not definitions) in some
places.
But
On Fri, Feb 6, 2009 at 1:10 AM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Fred Drake wrote:
On Thu, Feb 5, 2009 at 12:52 PM, Tres Seaver tsea...@palladion.com wrote:
I'm fixing dependent packages broken by my changes:
Summary of messages to the zope-tests list.
Period Thu Feb 5 12:00:00 2009 UTC to Fri Feb 6 12:00:00 2009 UTC.
There were 10 messages: 10 from Zope Tests.
Test failures
-
Subject: FAILED (failures=6) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Thu Feb 5 21:10:39 EST
2009/2/6 Martijn Faassen faas...@startifact.com:
Hey Dan and everybody,
I've taken the document Dan started and have reorganized it a bit and
added bits I know of what happened at the sprint last week. I've also
introduced an 'introduction' section which discusses the aim of many of
the
2009/2/6 Martijn Faassen faas...@startifact.com:
Yep. Also, as I said before I think we also need to use deprecation
warnings for imports that are not classes for persistent objects
(until Chiristian writes the tool to upgrade them :)).
As far as I understand in a recent discussion people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Korostelev wrote:
2009/2/6 Martijn Faassen faas...@startifact.com:
Yep. Also, as I said before I think we also need to use deprecation
warnings for imports that are not classes for persistent objects
(until Chiristian writes the tool to
Hi there,
On Fri, Feb 6, 2009 at 5:47 PM, Tres Seaver tsea...@palladion.com wrote:
[snip]
Martijn hoped for a tool which would help developers find places in
their code which used the BBB locations, in order to help them
modernize.
And to repeat, this tool was mostly created last week in the
On Feb 6, 2009, at 7:35 AM, Chris Withers wrote:
Jim Fulton wrote:
zope.configuration isn't a namespace package. It is simply a
package with subpackages.
Does setuptools support something like:
packagea:
packagea/__init__.py
packagea/amodule.py
packagea.something:
Chris Withers wrote at 2009-2-6 12:31 +:
...
I would find is very unintuitive when configuration were centralized
(in subpackages of zope.configuration) rather than modular.
Configuration belongs to the application or framework component
that depends on this configuration not to
Dan Korostelev wrote at 2009-2-6 14:10 +0300:
...
I still think we need to bug developers that they
need to upgrade their code with deprecation warnings, so we can
eventually remove old imports.
When you abuse deprecation warnings for minor cosmetic issues
you risk that deprecation warnings are
26 matches
Mail list logo
