Hi, It seems that the default behaviour of printing them to sys.stderr may fit our needs.
Regards, Markus > -----Ursprüngliche Nachricht----- > Von: users-boun...@lists.ironpython.com [mailto:users- > boun...@lists.ironpython.com] Im Auftrag von Markus Schaber > Gesendet: Montag, 4. April 2011 08:17 > An: Discussion of IronPython > Betreff: Re: [IronPython] Migration warnings to python 3 > > Hi, Dino, > > I guess this is okay, some things like string / Unicode semantics are > actually already like in Python 3. > > I'll skim the hosting API to find out how I can get those warnings in > hosted environment. > > Regards, > Markus > > Von: users-boun...@lists.ironpython.com [mailto:users- > boun...@lists.ironpython.com] Im Auftrag von Dino Viehland > > > We do support the -3 option which turns those warnings on but I don't > think we have as many warnings as CPython did. > > >> From: users-boun...@lists.ironpython.com > >> [mailto:users-boun...@lists.ironpython.com] On Behalf Of Markus > >> Schaber Hello, The current estimate for IronPython to implement python > 3 was "not before fall". So applications hosting IronPython must think > about paving a good migration path for their users. > >> AFAIR, the cPython implementation can spit out a bunch of warnings for > Code incompatible with cPython 3. > >> Is this mechanism supported by hosted IronPython? > > Grüße, > Markus > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
