Terry Reedy tjreedy at udel.edu
Mon Mar 7 20:45:57 CET 2011

• Previous message: [Python-Dev] PyCObject_AsVoidPtr removed from python 3.2 - is this documented?
• Next message: [Python-Dev] PyCObject_AsVoidPtr removed from python 3.2 - is this documented?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 3/7/2011 9:47 AM, Antoine Pitrou wrote:
> On Mon, 7 Mar 2011 19:14:55 +1000
> Nick Coghlan<ncoghlan at gmail.com>  wrote:
>> On Mon, Mar 7, 2011 at 6:36 PM, John Arbash Meinel
>> <john at arbash-meinel.com>  wrote:
>>>
>>> Especially since, AIUI, deprecations are suppressed by default now.
>>
>> True, but developers are expected to run their tests with them enabled.
>
> Where do we actually document this?

Should be, and maybe is, in the nice new dev guide.

Also, the doc for unittest.TextTestRunner says "By default this runner 
shows DeprecationWarning, PendingDeprecationWarning, and ImportWarning 
even if they are ignored by default." The idea (discussed here) is that 
developers of a module should see warnings when testing, even if users 
of the module do not. I am not sure whether above applies when running 
through unittest.main, but it should.

-- 
Terry Jan Reedy

---

• Previous message: [Python-Dev] PyCObject_AsVoidPtr removed from python 3.2 - is this documented?
• Next message: [Python-Dev] PyCObject_AsVoidPtr removed from python 3.2 - is this documented?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list