[Python-Dev] On breaking modules into packages Was: [issue10199] Move Demo/turtle under Lib/ (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Wed Nov 3 15:17:49 CET 2010
- Previous message: [Python-Dev] On breaking modules into packages Was: [issue10199] Move Demo/turtle under Lib/
- Next message: [Python-Dev] On breaking modules into packages Was: [issue10199] Move Demo/turtle under Lib/
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le mercredi 03 novembre 2010 à 14:16 +0000, Michael Foord a écrit :
On 03/11/2010 14:05, Nick Coghlan wrote: > On Wed, Nov 3, 2010 at 9:32 AM, Raymond Hettinger > <raymond.hettinger at gmail.com> wrote: >> Sounds like a decision to split a module into a package is a big commitment. Each of the individual file names becomes a permanent part of the API. Even future additional splits are precluded because it might break someones dotted import (i.e. not a single function can be moved between those files -- once in unittest.utils, alway in unittest.utils). > Can Python 2.7 pickles containing unittest classes be unpickled using > 2.6 or earlier? Even if nobody uses the new names for imports, I > believe they implicitly end up included in any pickles involving > affected classes (I seem to recall we've been bitten by that before > when moving things around).
Yes, since unittest.TestCase is still available (as are all the names). I believe so anyway...
unittest.TestCase is not really pickleable. There were test_multiprocessing issues because of that (see recent SVN checkins).
Regards
Antoine.
- Previous message: [Python-Dev] On breaking modules into packages Was: [issue10199] Move Demo/turtle under Lib/
- Next message: [Python-Dev] On breaking modules into packages Was: [issue10199] Move Demo/turtle under Lib/
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]