I'm currently trying out flit for a new project, and find it nicely simple to use. However, I've also found a current constraint in terms of the source tree layout: if you use a repo structure with a top level "src" directory, then the flit.ini file needs to be in that directory.
This means that in PEP 516 terms, the build command will need to be "flit -f src/flit.init" rather than just a plain "flit". I think the PEP could stand to be a bit more explicit that when the specified build_command is invoked, the current working directory will be the root of the source tree. (The PEP sort of implies this already, but I didn't see it explicitly stated anywhere) Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
