The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 FreeBSD
tmiddleton.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7927
Blamelist: andreasjung,ctheune
BUILD FAILED: failed svn
sincerely,
-The Buildbot
_
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7927
Blamelist: andreasjung,ctheune
BUILD FAILED: failed failed slave lost
sincerely,
-The Buildbot
Jeff Shell wrote:
Compare:
- http://dev.zope.org/Zope3/RoadMap
- http://www.sqlalchemy.org/trac/milestone/0.3.0?by=severity
Or dev.plone.org. Trac is pretty nice, especially as an svn browser and
for the roadmap view. The issue tracker is quite good (could be better,
but works fairly well)
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7925
Blamelist: andreasjung,ctheune
BUILD FAILED: failed failed slave lost
sincerely,
-The Buildbot
Christian Theune wrote:
Hi,
as I stumbled over this recently, I'd like to bring this up for discussion:
There is an interface called IWriteFile in the module
zope.filerepresentation.interfaces.
It defines one method "write(data)" with the doc string:
"Update the file data"
There are some pro
Philipp von Weitershausen wrote:
> Christian Theune wrote:
>> Hi,
>>
>> as I stumbled over this recently, I'd like to bring this up for
>> discussion:
>>
>> There is an interface called IWriteFile in the module
>> zope.filerepresentation.interfaces.
>>
>> It defines one method "write(data)" with th
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux tlotze.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7933
Blamelist: icemac
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-dev maili
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-9-28 11:22 +0200:
...
The last time this was discussed with Jim, the idea was to try to use
Zope 3's security proxy approach in Zope 2 for Python Script security
- Jim and I had some ideas I need to dredge up from the back of my
mind.
Jeff Shell wrote:
On 9/28/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
Christian Theune wrote:
> Morning,
>
> Baiju M wrote:
>> Hi,
>> What is the target Python version for Zope 3.4, is it Python 2.5?
>
> Right now it's still Python 2.4, as Zope 3.4 is scheduled for next
year,
>
Jeff Shell wrote:
On 9/28/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
Jim Fulton wrote:
Baiju M wrote:
Hi, What is the target Python version for Zope 3.4, is it
Python 2.5?
That's a good question. I fear it will take a fair bit of work
to get to it and, frankly for me there are higher pr
On 9/29/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
It's going to be a significant investment of work to make sure
everything works with Python 2.5. Either someone credible steps up,
convinces us, and does the work, and we all move over to Python 2.5. If
they don't, we do it the next cycle.
On 9/29/06, Baiju M <[EMAIL PROTECTED]> wrote:
On 9/29/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
> It's going to be a significant investment of work to make sure
> everything works with Python 2.5. Either someone credible steps up,
> convinces us, and does the work, and we all move over to
Baiju M wrote:
On 9/29/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
It's going to be a significant investment of work to make sure
everything works with Python 2.5. Either someone credible steps up,
convinces us, and does the work, and we all move over to Python 2.5. If
they don't, we do it t
Roy Mathew wrote:
I find that testing for security is hard, since the default user in
the doctests seems to have "unrestricted" access to all methods and
attributes. Is there a "unit-test friendly" way of faking a user
with a more restricted role, so that I can reproduce security errors
in unit t
Martijn Faassen wrote:
Again, I'll repeat that I think we should *not* trying to support two
Python versions at the same time. Whether something works on a later
version of Python is beside the point; it's about whether we officially
make sure. I do not believe we currently (if ever) want to sp
Thanks for the input. I wonder if anyone wants to volunteer to
spearhead a track prototype for zope.org? One of the things I like
about Launchpad is that I don't have to do any work. If someone is
willing to step forward and commit to a Trac implementation, I'm happy
to try it out. I'd like t
Baiju M wrote:
On 9/29/06, Baiju M <[EMAIL PROTECTED]> wrote:
On 9/29/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
> It's going to be a significant investment of work to make sure
> everything works with Python 2.5. Either someone credible steps up,
> convinces us, and does the work, and we a
Benji York wrote:
Martijn Faassen wrote:
Again, I'll repeat that I think we should *not* trying to support two
Python versions at the same time. Whether something works on a later
version of Python is beside the point; it's about whether we
officially make sure. I do not believe we currently (
Tres Seaver wrote:
...
The change from 2.4 to 2.5 is *massively* disruptive for a framework
like Zope: much more so than any change since 2.2, I think (maybe even
2.0/2.1). The hardest bit is the change to the way the compiler works:
RestrictedPython is completely incompatible with the new AST
>> On a small aesthetics side, I find Launchpad's side bars incredibly
>> distracting, and I don't like looking at the page because it feels
>> like there are too many things vying for my attention and I have a
>> hard time really reading the text in front of me. The content gets
>> squished. And
On Sep 29, 2006, at 10:03 AM, Jim Fulton wrote:
Tres Seaver wrote:
...
The change from 2.4 to 2.5 is *massively* disruptive for a framework
like Zope: much more so than any change since 2.2, I think (maybe
even
2.0/2.1). The hardest bit is the change to the way the compiler
works:
Rest
Martijn Faassen wrote:
>
> Before we move any issue collectors to launchpad, we need a bit more
> experience with the launchpad issue tracker and its capabilities.
The first couple of links on https://help.launchpad.net/ are to
"Highlights of feature planning" and "Highlights of bug tracking"
docu
> Finally, I'm experimenting with using launchpad for bugs:
>
> https://launchpad.net/products/zc.buildout/+bugs
>
> and feature requests:
>
> https://features.launchpad.net/products/zc.buildout/
>
> So far this is working OK. I haven't really stressed it. Launchpad makes
> this very easy
Philipp von Weitershausen wrote:
> Christian Theune wrote:
>> Hi,
>>
>> as I stumbled over this recently, I'd like to bring this up for
>> discussion:
>>
>> There is an interface called IWriteFile in the module
>> zope.filerepresentation.interfaces.
>>
>> It defines one method "write(data)" with t
Christian Theune wrote:
We probably have to. But to be honest? I totally understand every
programmer that will ask us "WTF?!?". Does anybody see a better way out
of that situation without deprecating anything again?
I don't. As far as I can tell, this is a deceptive API and looks like a
perfe
Roy Mathew wrote:
> I find that testing for security is hard, since the default user in
> the doctests seems to have "unrestricted" access to all methods and
> attributes. Is there a "unit-test friendly" way of faking a user
> with a more restricted role, so that I can reproduce security errors
>
On 9/29/06, Steve Alexander <[EMAIL PROTECTED]> wrote:
>> On a small aesthetics side, I find Launchpad's side bars incredibly
>> distracting, and I don't like looking at the page because it feels
>> like there are too many things vying for my attention and I have a
>> hard time really reading th
>> There is an interface called IWriteFile in the module
>> zope.filerepresentation.interfaces.
>>
>> It defines one method "write(data)" with the doc string:
>>
>> "Update the file data"
>>
>> There are some problems I have with this:
>>
>> a) The interface is yet another interface for doing
On Sep 29, 2006, at 5:08 PM, Luis De la Parra wrote:
then we have z3c.filetype and zope.mimetype. For what I've seen,
z3c.filetype is in a better shape, but both of them seem to be
similar.
I'm not familiar with z3c.filetype. Could you (or someone else)
elaborate on the similarities, and
Benji York wrote:
Christian Theune wrote:
We probably have to. But to be honest? I totally understand every
programmer that will ask us "WTF?!?". Does anybody see a better way out
of that situation without deprecating anything again?
I don't. As far as I can tell, this is a deceptive API and
30 matches
Mail list logo
