[Python-Dev] [Python-checkins] Things to remember when adding *packages* to stdlib
Neal Norwitz
nnorwitz at gmail.com
Tue Jun 27 06:37:50 CEST 2006
More information about the Python-Dev mailing list
Tue Jun 27 06:37:50 CEST 2006
- Previous message: [Python-Dev] [Python-checkins] Things to remember when adding *packages* to stdlib
- Next message: [Python-Dev] Switch statement
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/25/06, "Martin v. Löwis" <martin at v.loewis.de> wrote: > Neal Norwitz wrote: > > I believe this change is all that's necessary on the Unix side to > > install wsgiref. Can someone please update the Windows build files to > > ensure wsgiref is installed in b2? Don't forget to update the NEWS > > entry too. > > It's installed in b1 already. The msi generator picks up all .py files > in Lib automatically, except for those that have been explicitly > excluded (the plat-* ones). Ah cool. I was confusing it with extensions and mis-remembering. > > Maybe someone could come up with a heuristic to add to Misc/build.sh > > which we could test in there. > > I think "make install INSTALL=true|grep true" should print the names > of all .py files in Lib, except for the ones in plat-*. I modified the build.sh script to run the installed version. As long as some test references the new package, this should catch the problem. I sure hope we don't allow a new package without tests. :-) I also modified the buildbot config to ignore changes if all the files in a revision are under Demo, Doc, or Misc. This change (if I got it right and it works) should help reduce some builds that have little benefit. n
- Previous message: [Python-Dev] [Python-checkins] Things to remember when adding *packages* to stdlib
- Next message: [Python-Dev] Switch statement
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list