Not sure whether this should be separate commits, or 1 single commit?

How to resolve the setup.py condition on Python 2?

    extras_require={
        ":python_version<'3.0'": ['futures'],
    },

Not sure whether this should be separate commits, or 1 single commit?

Separate ones. And they should have pythonPackages in the commit message.

How to resolve the setup.py condition on Python 2?

+ lib.optional (!isPy3k) futures

Where do I get isPy3k from?

Where do I get isPy3k from?

as an argument

I'm going to use lib.optional. However I realised that there's a dependency graph here and thankfully not mutually dependent. So there's going to be an order to these commits too.

Just a note lib.optionals allows a list of dependencies.

How do I do this? "Determined the impact on package closure size (by running nix path-info -S before and after)"

@dotlambda Edits are all done.

I changed PR name.

@dotlambda Strange, how the commit log is on a different order to this PR's commits. I committed azure-storage-nspkg first, but it appears that Github bot is testing the last commit first.

Related to: https://stackoverflow.com/questions/44704519/how-to-fix-commit-order-in-github-pull-requests-broken-by-git-rebase

Aside from that these all build for me locally.

All edits done, still don't quite understand why the commit order is different though.

@CMCDragonkai Sorry, I forgot to tell that we need a comment at every doCheck = false; like

# Has no tests

I'm always forget that one 😄

Done.

Thanks again 👍