(I left header so Ben knows he wrote it...) On Sun, Jun 15, 2008 at 06:36, Ben Finney <[EMAIL PROTECTED]> wrote: > I'm most of the way along with a branch that has the following > purpose: > > Move all non-program modules into a Python package directory, > 'reportbuglib/', and ensure all imports still work. > > Now, 'reportbuglib' may not be the best choice of name, but the name > should be relatively simple to change later if we decide to. It also > avoids the concerns raised earlier about a package named 'reportbug' > and a program of the same name. > > This branch doesn't do anything about moving *programs* around; they > will still be testable in-place. Nor does it address the "use > distutils" or "use setuptools" ideas. It's intended to be a minimal > change, to meet the above limited goal. > > I expect to have this branch ready to merge into trunk fairly soon. > Does anyone have any objection to me doing so?
My only concern is: do you really think that a package with 200+ bugs opened need aestetical or architectural changes instead of bugfixes? Of course, you're the expert here, so I won't argue... The only thing that worths be added, is having an arch doc, that explains the code structure, relationship and so, a sort of high-level overview of the code. Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi _______________________________________________ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
