On 05/19/2012 05:59 PM, Tres Seaver wrote:
> On 05/19/2012 12:12 PM, Jim Fulton wrote:
>> I propose that these deprecation warnings be removed.
>
> I can do that, if that is the consensus.
Now done, and released as zope.interface 4.0.1.
Tres.
--
===
On 05/21/2012 04:49 AM, Gediminas Paulauskas wrote:
> 2012/5/20 Tres Seaver :
>> On 05/19/2012 07:23 PM, Jim Fulton wrote:
>>> On Sat, May 19, 2012 at 5:59 PM, Tres Seaver
>>> wrote:
>> They already do: 4.0.0 makes them exceptions under Python3: that
>> fact was actually my rationale for the war
On 05/20/2012 04:28 PM, Lennart Regebro wrote:
> On Sun, May 20, 2012 at 6:08 AM, Tres Seaver
> wrote:
>> I will release a 4.0.1 silencing the warnings unless somebody speaks
>> up in their favor.
>
> We should make sure we have 2to3 fixers for everything change as
> well. I added some fixers, bu
On Sun, May 20, 2012 at 10:42 PM, Jim Fulton wrote:
> Except that most of us aren't going to use 2to3, except for an initial
> stab at porting to 2&3.
Which is good enough. You only need to run it once.
//Lennart
___
Zope-Dev maillist - Zope-Dev@zope
On Sun, May 20, 2012 at 12:08:14AM -0400, Tres Seaver wrote:
> On 05/19/2012 07:23 PM, Jim Fulton wrote:
> > On Sat, May 19, 2012 at 5:59 PM, Tres Seaver
> > wrote:
> >> On 05/19/2012 12:12 PM, Jim Fulton wrote:
> >>> The declaration-syntax warnings in the zope.interface 4.0.0 are
> >>> annoying
2012/5/20 Tres Seaver :
> On 05/19/2012 07:23 PM, Jim Fulton wrote:
>> On Sat, May 19, 2012 at 5:59 PM, Tres Seaver
>> wrote:
>>> On 05/19/2012 12:12 PM, Jim Fulton wrote:
The declaration-syntax warnings in the zope.interface 4.0.0 are
annoying and mostly pointless.
There will
On Sun, May 20, 2012 at 4:28 PM, Lennart Regebro wrote:
> On Sun, May 20, 2012 at 6:08 AM, Tres Seaver wrote:
>> I will release a 4.0.1 silencing the warnings unless somebody speaks up
>> in their favor.
>
> We should make sure we have 2to3 fixers for everything change as well.
> I added some fix
On Sun, May 20, 2012 at 6:08 AM, Tres Seaver wrote:
> I will release a 4.0.1 silencing the warnings unless somebody speaks up
> in their favor.
We should make sure we have 2to3 fixers for everything change as well.
I added some fixers, but it's so long ago I'm not sure all changes are
covered. Bu
On Sun, May 20, 2012 at 12:08 AM, Tres Seaver wrote:
> On 05/19/2012 07:23 PM, Jim Fulton wrote:
...
>> I'd forgotten the fail silently bit. Can't we make the fail loudly
>> for Python 3?
>
> They already do: 4.0.0 makes them exceptions under Python3: that fact
> was actually my rationale for
On 05/19/2012 07:23 PM, Jim Fulton wrote:
> On Sat, May 19, 2012 at 5:59 PM, Tres Seaver
> wrote:
>> On 05/19/2012 12:12 PM, Jim Fulton wrote:
>>> The declaration-syntax warnings in the zope.interface 4.0.0 are
>>> annoying and mostly pointless.
>>>
>>> There will be enough pain in porting appli
On Sat, May 19, 2012 at 5:59 PM, Tres Seaver wrote:
> On 05/19/2012 12:12 PM, Jim Fulton wrote:
>> The declaration-syntax warnings in the zope.interface 4.0.0 are
>> annoying and mostly pointless.
>>
>> There will be enough pain in porting applications to Python 3,
>> avoiding the surprise of havi
On 05/19/2012 12:12 PM, Jim Fulton wrote:
> The declaration-syntax warnings in the zope.interface 4.0.0 are
> annoying and mostly pointless.
>
> There will be enough pain in porting applications to Python 3,
> avoiding the surprise of having to use a different
> interface-declaration syntax wil
The declaration-syntax warnings in the zope.interface 4.0.0 are
annoying and mostly pointless.
There will be enough pain in porting applications to Python 3,
avoiding the surprise of having to use a different
interface-declaration syntax will not be of any consequence.
While the deprecation warni
13 matches
Mail list logo
