Barry Warsaw writes:
> On Aug 10, 2009, at 9:42 PM, Ben Finney wrote:
> > I ask because I haven't seen any messages reach the
> > ‘comp.lang.python’ Usenet group since this report. Is that related?
>
> Hmm, if you're getting this message then mailing lists should be
> working. I don't know what
2009/8/11 Jacob Rus :
>
> I have some other questions: How does one deprecate part of a standard
> library API? How can we alert users to the deprecation? When can the
> deprecated parts be removed?
Basically, you add a DeprecationWarning to the API. Then remove it in
the next major version.
If
Jacob Rus wrote:
> Well, I've had some patches up at http://bugs.python.org/issue6626 for
> over a week now, and my updated version should have identical
> semantics to the current module, just with the module's *actual*
> behavior clear to anyone reading the code, some serious edge-case bugs
> fix
Glyph Lefkowitz wrote:
> Jacob Rus wrote:
> No, [changing the semantics in 3.x] is bad. If I may quote Guido:
> http://www.artima.com/weblogs/viewpost.jsp?thread=227041
>
>> So, once more for emphasis: Don't change your APIs at the same time as
>> porting to Py3k!
>
> Please follow this policy as
On Mon, Aug 10, 2009 at 21:12, Thomas Wouters wrote:
>
>
> On Sat, Aug 8, 2009 at 22:22, A.M. Kuchling wrote:
>
>> The following sites are up again on a new machine, but cannot be
>> updated through SVN hooks or whatever mechanism:
>>
>> www.python.org
>> docs.python.org
>> www.jython.org
>> pla
