-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/04/14 14:37, David King wrote: > ... because of the author's opinions of the standard Python ways to > require packages
As said author, the problem is that pip etc authors chose to make it impossible to provide arguments to parts of the install process[1]. APSW uses those arguments to control things like fetching SQLite source, which extensions to enable and things affecting SQLite like if extension loading is supported. I could pick some defaults but they will always be wrong for some subset of people. It is also fairly hairy to make this all work from a build perspective. I'll likely end up hacking some defaults at some point. Also for the record I haven't seen a patch from you to fix the issue in a way you deem acceptable :-) When I distributed Python applications in the past (eg BitPim) I bundled everything up so Python being used was not visible (nor relevant) to the user. This approach worked fine on Windows, Linux and Mac. [1] distutils - a standard part of python - is used under the hood which has multiple subcommands each of which can be given flags. pip etc ultimately call into that. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlM93bkACgkQmOOfHg372QTx4wCgss8x7+Vymm7pZZDQ4X9+pLH5 D6IAoKF39KgDU95UesVtiFESluNGHv9s =+r3t -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
