On Tue, Dec 15, 2015 at 12:30 PM, Paul Moore <[email protected]> wrote:
> I guess you're saying add [speedups] as a way of requesting a rebuild? > But if the build fails, would that remove sqlalchemy, or leave the > existing build there? (I'd hope the latter). > Well in this world of wheels we aren't necessarily building anything right.. so there's no "rebuild" or "build". We are just unzipping a bdist and some optional deps. I've seen in the past that a recommended way of accomplishing this would be to create an sqlalchemy-cext package on pypi and have sqlalchemy depend on it. This is what I meant with the "cext": "sqlalchemy-cext" extra. Then people who wanted speedups (most people obviously) would depend on sqlalchemy[cext]. This example works entirely within the current framework. Where I'm at is that it'd be nice if it were extended to support "recommends" or "default extras" but have some way for the extra to not be installed on systems that couldn't handle it (via metadata cross-checked with system/python info).
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
