Hi,
Philipp von Weitershausen wrote:
> I want to make most of the browser:* directives saner in implementation,
> without actually changing their behaviour, though. Unless people want to
> make their behaviour saner, too ;).
I wouldn't mind making myself behave saner. :)
As we're at it: I forgot
Christian Theune wrote:
Hi,
Philipp von Weitershausen wrote:
I want to make most of the browser:* directives saner in implementation,
without actually changing their behaviour, though. Unless people want to
make their behaviour saner, too ;).
I wouldn't mind making myself behave saner. :)
As
Hi,
Philipp von Weitershausen wrote:
> Christian Theune wrote:
>> Hi,
>>
>> Philipp von Weitershausen wrote:
>>> I want to make most of the browser:* directives saner in implementation,
>>> without actually changing their behaviour, though. Unless people want to
>>> make their behaviour saner, too
Baiju M wrote:
Hi,
What is the target Python version for Zope 3.4, is it Python 2.5?
That would be loverly for both 3.4 and 2.11 :-D
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Z
Jim Fulton wrote:
That's pretty much what I suggested. The whole point of discriminators
was conflict detection. That is why I suggested extending actions to
support identifiers that could be used for overriding or disabling even
for actions (or groups of actions) that don't otherwise confl
Philipp von Weitershausen 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,
we should consider using Python 2.5 though.
We should definitely
Martijn Faassen wrote:
Philipp von Weitershausen 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,
we should consider using Python 2.5 though
2006/9/27, Philipp von Weitershausen <[EMAIL PROTECTED]>:
On behalf of the Zope 3 development team I'm proud to announce the final
Zope 3.3.0 release. There were no changes since the 3.3.0 release candidate.
...
Thanks goes to everyone who contributed.
There aren't AUTHORS file (zope 3 aut
KLEIN Stéphane wrote:
2006/9/27, Philipp von Weitershausen <[EMAIL PROTECTED]>:
On behalf of the Zope 3 development team I'm proud to announce the final
Zope 3.3.0 release. There were no changes since the 3.3.0 release
candidate.
...
Thanks goes to everyone who contributed.
There aren't
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 priorities.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7911
Blamelist: faassen,romanofski
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
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: 7911
Blamelist: faassen,romanofski
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
Z
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7911
Blamelist: faassen,romanofski
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
Christian Theune wrote:
Hi,
I saw some updates in the wiki tonight and thought I'll catch up with
some stuff too.
As I opted to take care for the Zope 3.4 release and Zope 3.3 is out of
the door since yesterday, I've updated the roadmap.
http://www.zope.org/Wikis/DevSite/Projects/ComponentArc
Motivated by a Zope 2.9.5 release this weekend, I'll be creating a 3.2.2
bugfix release this Saturday. I encourage everyone to get bugfixes into
the 3.2 branch till then, especially if you've fixed a bug in Zope 3.3
recently (e.g. one of the bugdays) and haven't backported it yet.
By the way,
Chris Withers wrote:
Baiju M wrote:
Hi,
What is the target Python version for Zope 3.4, is it Python 2.5?
That would be loverly for both 3.4 and 2.11 :-D
I think it will require a huge effort to get Zope 2 working with
Python 2.5. Either:
- We need to change Zope 2 to use Zope 3's securi
Hello Philipp,
Thursday, September 28, 2006, 3:48:34 PM, you wrote:
> By the way, it'd be cool if someone could do the Windows release. See
> http://dev.zope.org/Zope3/ZopeWindowsRelease for more info.
I'm raising my hand. Doing it is OK, Updating the wiki page will take
some time.
--
Best re
Jim Fulton wrote:
>> As I opted to take care for the Zope 3.4 release and Zope 3.3 is out of
>> the door since yesterday, I've updated the roadmap.
>
> http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/RoadMap
Jup.
> I think we should move the alpha and beta schedules up. IMO, we
Martijn Faassen wrote:
Philipp von Weitershausen 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,
we should consider using Python 2.5 though
Hello Philipp,
BTW, correct me if I'm wrong, bugfixes go into:
/repos/main/Zope3/branches/3.2
and
/repos/main/Zope3/branches/3.3
Releases get built from:
/repos/main/Zope3/tags/Zope-3.2.2
and
/repos/main/Zope3/tags/Zope-3.3.1
--
Best regards,
Groszer Adam
--
Quote of the day:
Feast, and your h
Adam Groszer wrote:
Hello Philipp,
BTW, correct me if I'm wrong, bugfixes go into:
/repos/main/Zope3/branches/3.2
and
/repos/main/Zope3/branches/3.3
... and the trunk. Correct.
Releases get built from:
/repos/main/Zope3/tags/Zope-3.2.2
and
/repos/main/Zope3/tags/Zope-3.3.1
Yup.
___
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7913
Blamelist: fdrake,romanofski,yusei
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
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: 7913
Blamelist: fdrake,romanofski,yusei
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7913
Blamelist: fdrake,romanofski,yusei
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
__
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 priorities.
I think we'd be okay in not supporting Python 2.5 yet for thi
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.
I am quit
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
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,
> we should consider us
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,
>
Hi everybody.
I noticed this in the roadmap.
Planned schedule
* Zope 3.4 alpha 1: mid-April, 2006
* Zope 3.4 beta 1: first week in May, 2006
* Zope 3.4 RC 1: mid-May, 2006
* Zope 3.4 final: last week of May, 2006
Shouldn't those be 2007?
___
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 prioritie
Hi
A small introduction, as I believe this is my first post to this list.
My name is Jacob, and I am the CTO of a small danish software company
named Improva. We have been selling Zope2 based solutions since
somewhere around version 2.5.1, and we started using Zope3 when ZopeX3
came out. Amon
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7921
Blamelist: faassen,fdrake,jim,romanofski,wosc,yuppie,yusei
BUILD FAILED: failed test
sincerely,
-The Buildbot
_
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.
On 9/25/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
Baiju M wrote:
> On 9/22/06, Jim Fulton <[EMAIL PROTECTED]> wrote:
>
>> Finally, I'm experimenting with using launchpad for bugs:
>>
>>https://launchpad.net/products/zc.buildout/+bugs
>>
>> and feature requests:
>>
>>https://features
Hi Folks,
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 tests?
T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 ta
--On 28. September 2006 16:17:54 -0400 Jim Fulton <[EMAIL PROTECTED]> wrote:
We should definitely try to *support* Python 2.5, but we can't require
it till Zope 2 has been "certified" for it.
Why isn't Python 2.5 even supported at present?
There are lots of test failures. Also, untrusted P
Douglas Douglas wrote:
> Hi everybody.
>
> I noticed this in the roadmap.
>
> Planned schedule
>
> * Zope 3.4 alpha 1: mid-April, 2006
> * Zope 3.4 beta 1: first week in May, 2006
> * Zope 3.4 RC 1: mid-May, 2006
> * Zope 3.4 final: last week of May, 2006
>
> Shouldn't those b
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 problems I have with this:
a
41 matches
Mail list logo