Where would the automated test code live? If it's inside Nevow proper, does that mean it would import setup.py in a unit test module?
Should we move the parsing code inside of Nevow, then import that in setup.py? That difficult without re-introducing the problem this patch is trying to solve. It would also be in danger of regressing https://bugs.launchpad.net/nevow/+bug/812537. Should the setup.py module itself could have unittests? All of these options sound ridiculous to me. Is there another approach I've missed? It seems like the right way to test this is to have package infrastructure tests somewhere that test installing packages (and then running the unittests or other verification on the installation). Does Nevow have such a system? If not, I can try one of the approaches above, and I'd appreciate guidance on which is the least insane. -- https://code.launchpad.net/~nejucomo/divmod.org/fix-nevow-setup/+merge/176026 Your team Divmod-dev is subscribed to branch lp:divmod.org. -- Mailing list: https://launchpad.net/~divmod-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~divmod-dev More help : https://help.launchpad.net/ListHelp
