On Thu, Aug 21, 2008 at 8:45 AM, Thomas Lotze <[EMAIL PROTECTED]> wrote:
> If someone gives me access to the package on PyPI (username: tlotze),
> I can also upload it there.
Done.
-Fred
--
Fred L. Drake, Jr.
"Chaos is the score upon which reality is written." --Henry Miller
Tres Seaver wrote:
> Thomas Lotze wrote:
>> Oh well, it turns out that this doesn't really work well as the class in
>> question is used as a base class by all the items edit widgets. The
>> next-best approach we'd try would be a module-global flag that turns the
>> old behaviour back on and must
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Lotze wrote:
> Thomas Lotze wrote:
>
>> Roger Ineichen wrote:
>>
>>> Since this is a miss behavior and I agree that this should get fixed. We
>>> probably should think about a solution which supports the old behavior
>>> by default.
>>>
>>> Not
Thomas Lotze wrote:
> Roger Ineichen wrote:
>
>> Since this is a miss behavior and I agree that this should get fixed. We
>> probably should think about a solution which supports the old behavior
>> by default.
>>
>> Note, this whould probably also break other packages like
>> z3c.csvvocabulary.
Roger Ineichen wrote:
> Since this is a miss behavior and I agree that this should get fixed. We
> probably should think about a solution which supports the old behavior by
> default.
>
> Note, this whould probably also break other packages like
> z3c.csvvocabulary.
We've thought about this some
Hi Thomas
> Betreff: Re: [Zope-dev] zope.app.form: Make "no value" always
> available?
[...]
> > If nobody else objects I'm fine with this changes and will
> fix a Zope3
> > revision for this project and start to migrate to z3c.form.
> We have to
>
Roger Ineichen wrote:
> I agree with this but...
> The 2750 test in one of our well tested application will explode. And
> probably some tests in the zope core and z3c will break too.
>
> Since this is a miss behavior and I agree that this should get fixed. We
> probably should think about a solu
Hi Thomas
> Betreff: [Zope-dev] zope.app.form: Make "no value" always available?
>
> zope.app.form items edit widgets don't provide the "no value"
> value if the corresponding field is required. While this
> prevents invalid input, it means that e.g. a drop-down box
> may then have one of the
Thomas Lotze wrote:
> zope.app.form items edit widgets don't provide the "no value" value if
> the corresponding field is required. While this prevents invalid input, it
> means that e.g. a drop-down box may then have one of the valid values
> pre-selected. If user forgets to change that value, he
