akuchlin@mems-exchange.org wrote: > On Tue, May 28, 2002 at 06:20:54PM +0200, M.-A. Lemburg wrote: > >>The migration path, including hints on how to port Python applications > >>from one version to the next, how to work around deprecations, > >>tips on quick ways to find problem areas in the code, etc. > > > Part of the problem is that I work from the CVS logs and from the > Misc/NEWS file, and people don't always indicate when a potential > incompatibility is introduced. (That may not be clear to the person > making the change, of course, if they think they're changing an > obscure bit of code.) > > I'd certainly like to point out required changes. The 2.0 document > had a "Porting to 2.0" section, but now I generally try to cover such > issues in the section for the relevant PEP. You're doing a great hob here, Andrew ! What should we do to make your work easier ? -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/ Meet us at EuroPython 2002: http://www.europython.org/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4