On 2010-7-21 07:32, Wolfgang Schnerring wrote:
> * Wichert Akkerman [2010-07-20 19:28]:
>> On 2010-7-20 18:15, Christian Theune wrote:
>>> At least, WRT this bug, I don't think it's a good idea to ask explicitly
>>> for bad requests to go to the application as the test layer should model
>>> real
On 07/21/2010 09:17 AM, Wichert Akkerman wrote:
> On 2010-7-21 07:32, Wolfgang Schnerring wrote:
>> * Wichert Akkerman [2010-07-20 19:28]:
>>> On 2010-7-20 18:15, Christian Theune wrote:
At least, WRT this bug, I don't think it's a good idea to ask explicitly
for bad requests to go to t
Summary of messages to the zope-tests list.
Period Tue Jul 20 12:00:00 2010 UTC to Wed Jul 21 12:00:00 2010 UTC.
There were 59 messages: 6 from Zope Tests, 1 from buildbot at
enfoldsystems.com, 4 from buildbot at pov.lt, 15 from buildbot at
winbot.zope.org, 13 from ccomb at free.fr, 20 from jdrie
I've ported zope.hookable too, but I don't need it until it's time to
port zope.component (and I think the same goes for zope,security which
I think is next if I remember correctly), so I'm not merging the
branch yet. It's full if ugly Python 3 hacks, as it's a c-extension.
Feel free to take a look
On Wed, Jul 21, 2010 at 06:28, Christian Theune wrote:
> I myself prefer having more releases. I like Marius' idea: 3.10 would be
> good for removing the test runner then 4.0 can be Py3 compatibility.
OK, I'll merge and release 3.10 today or tomorrow or so.
--
Lennart Regebro, Colliberty: http:
On Tue, Jul 20, 2010 at 23:57, Marius Gedminas wrote:
>> 1. Should there be BBB imports of zope.testrunner into zope.testing?
>> We can do that to get a longer deprecation period, a couple of months
>> isn't very long).
>
> *shrug*
Nobody said "YES!" and since it actually requires that zope.testi
On Wednesday, July 21, 2010, Lennart Regebro wrote:
> Nobody said "YES!" and since it actually requires that zope.testing
> depends on zope.testrunner to be pracically useful, I think we'll skip
> it.
I think nobody cares because everyone uses the test runner recipe. As long as
that recipe works,
On Tue, Jul 20, 2010 at 12:32 PM, Lennart Regebro wrote:
> I'd like to put down some effort this week during the EuroPython
> sprint to go forward with zope.testing for Python 3. zope.testing
> 3.9.5 is already deprecating zope.testing.testrunner, but I need to
> remove it so that I can port zope.
On Wed, Jul 21, 2010 at 15:06, Jim Fulton wrote:
> Do whatever is easiest for you. One option would be to release as
> eggs for Python 3 only. That way, you shouldn't be affecting Python 2
> users.
I've released 3.10.0 now, and will let that simmer a while. I'm on
Europython so please mail me i
On Mon, Jan 11, 2010 at 17:52, Hanno Schlichting wrote:
> On Mon, Jan 11, 2010 at 4:31 PM, Roger wrote:
>> The zope.componentvocabulary package defines some
>> basic vocabulary (factory) classes. Probably we
>> should move the zope/app/schema/vocabulary.py
>> to this package as registry.py.
>
> I
On 7/21/10 6:19 PM, Patrick Gerken wrote:
> On Mon, Jan 11, 2010 at 17:52, Hanno Schlichting wrote:
>
>> On Mon, Jan 11, 2010 at 4:31 PM, Roger wrote:
>>
>>> The zope.componentvocabulary package defines some
>>> basic vocabulary (factory) classes. Probably we
>>> should move the zope/app/
11 matches
Mail list logo
