Hi Marius,
Your fix of browser.py causes problems for me using hurry.file when
running functional test with zope.testbrowser.
The problem is that aFieldStorage.filename is already unicode and it
cannot be decoded again.
Do you mind if I add an
if isinstance(aFieldStorage.filename, unicode):
const
Hmm, this seems strange to me. How can it be guaranteed that the remote
filename is a utf-8 encoded byte string? Not sure this should be done
this way anyhow.
- Rocky
On Mon, 2006-19-06 at 11:01 +0200, Adam Groszer wrote:
> Hi Marius,
>
> Your fix of browser.py causes problems for me using h
Hello!
Currently I'm working on the issue 525 ("DateWidget ru-format"). I've already
changed 'parseDatetimetz' in favor of 'self.request.locale.dates.getFormatter'
for DatetimeWidget and DateWidget, but now I face some usability/backward
compatibility problems.
By default display style for '
Lennart Regebro wrote:
On 6/18/06, Paul Winkler <[EMAIL PROTECTED]> wrote:
+1, I'd like some way to easily know when a release is no longer
maintained. i.e., what's the X in the above formula.
Well, it's 2 versions, so far. I.e, current release and last release.
Unless we decide to change tha
Philipp von Weitershausen wrote:
Note that this should also extend to the Zope 3 releases. Zope 3.2 is
part of Zope 2.9 and will hence be used for quite some time. Yet,
bugfixes aren't even backported to the Zope 3.2 branch anymore...
It's this sort of thing that makes me wish we could unify th
Christian Theune wrote:
However, Zope 2.8 is still available for stable download ... so we
currently have 7 branches to watch out for.
...and you're not even including ZODB branches and the like that need to
be maintained and kept in sync...
Chris
--
Simplistix - Content Management, Zope &
Chris Withers wrote:
> Philipp von Weitershausen wrote:
>> Note that this should also extend to the Zope 3 releases. Zope 3.2 is
>> part of Zope 2.9 and will hence be used for quite some time. Yet,
>> bugfixes aren't even backported to the Zope 3.2 branch anymore...
>
> It's this sort of thing tha
Philipp von Weitershausen wrote:
Uh, never mind.
+1 :)
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
On 6/19/06, Chris Withers <[EMAIL PROTECTED]> wrote:
> Well, it's 2 versions, so far. I.e, current release and last release.
> Unless we decide to change that now.
Is it really?
That's how it has been so far, yes. Maybe we should extend it. But
mind you, that's more work...
I for one, is NOT
On 6/19/06, Lennart Regebro <[EMAIL PROTECTED]> wrote:
I for one, is NOT interested in backporting fixed in Five trunk to
both Five 1.0, 1.1, 1.3, 1.4 and 1.5, which is what are the current
versions of Five if we say that Zope 2.8 and 2.7 should be still
supported after the release of 2.10. If so
--On 19. Juni 2006 16:25:32 +0200 Lennart Regebro <[EMAIL PROTECTED]> wrote:
I for one, is NOT interested in backporting fixed in Five trunk to
both Five 1.0, 1.1, 1.3, 1.4 and 1.5, which is what are the current
versions of Five if we say that Zope 2.8 and 2.7 should be still
supported after
On Mon, 2006-19-06 at 11:01 +0200, Adam Groszer wrote:
> Hi Marius,
>
> Your fix of browser.py causes problems for me using hurry.file when
> running functional test with zope.testbrowser.
> The problem is that aFieldStorage.filename is already unicode and it
> cannot be decoded again.
>
> Do you
Hi,
On Sun, Jun 18, 2006 at 01:33:48AM -0400, Christian Theune wrote:
> I'm pretty confident that this change does what it is intended to do
> (fix 592 and some inconsistencies along the way).
>
> But as I had to figure out some pretty old code and some of the
> architecture and dependencies in
On Mon, Jun 19, 2006 at 07:59:07PM +0300, Marius Gedminas wrote:
> On Sun, Jun 18, 2006 at 01:33:48AM -0400, Christian Theune wrote:
> > I'm pretty confident that this change does what it is intended to do
> > (fix 592 and some inconsistencies along the way).
> >
> > But as I had to figure out so
Marius Gedminas wrote:
I don't mind, but I think it would be better if testbrowser was changed
to match what real browsers do instead.
+1
However, we'd have to decide who is creating the unicode string:
testbrowser, mechanize, or the publishing framework.
--
Benji York
Senior Software Engine
Hi,
due to the discussion in issue 507 and to make Zope 3 and Zope 2 behave
more similar, I propose to disable the developer mode by default as of
Zope 3.3 and as an additional fix for Zope 3.2.
Additionally, I might take the time to log a warning when in developer
mode, and even more additi
On 6/19/06, Christian Theune <[EMAIL PROTECTED]> wrote:
Additionally, I might take the time to log a warning when in developer
mode, and even more additionally, I'll introduce a red blinking
something that tells you in the ZMI that you are running developer mode.
+1 to all this!
-Fred
--
Fr
Hello Benji, Marius,
Sorry, "entwarnung"
It is hurry.file causing the the problem, it is doing
def _toFormValue(self, value):
if value == self.context.missing_value:
return self._missing
return FileUpload(FakeFieldStorage(value.filename, value.data))
and this FileUplo
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: 6254
Blamelist: benji_york,ctheune,jim
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
19 matches
Mail list logo
