On Dec 9, 10:37 pm, rusi <rustompm...@gmail.com> wrote: > On Dec 9, 9:03 pm, Terry Reedy <tjre...@udel.edu> wrote: > > > > > On 12/9/2010 7:12 AM, rusi wrote: > > > > On Dec 9, 1:39 pm, Terry Reedy<tjre...@udel.edu> wrote: > > >> On 12/9/2010 1:10 AM, rusi wrote: > > > >>> I am unable to get trace to not trace system modules. > > > >> Try it with 3.2b1, just released. Multiple bugs were fixed in trace. > > >> Some fixes might also be in recent 2.7.1 and 3.1.3. Not sure. > > > >> -- > > >> Terry Jan Reedy > > > > I am doing this to port a 2.x app to 3 which is giving me a hell of a > > > time! :-; > > > I would get it to run on 2.7 first, with out getting any > > DeprecationWarnings when they are turned on. They are off by default and > > I am not sure how to turn on but presume the warnings module doc says how. > > > -- > > Terry Jan Reedy > > This is a bit of a headache... > Am on debian unstable but no 2.7 in the repos so I'll have to compile > it... > Ok can do that but first I'd like to check that this trace 'bug' has > been cleared > Where do I look?
Ok Ive got 2.7 from 'experimental' without any (apparent) glitches -- http://mail.python.org/mailman/listinfo/python-list
