Simplified the logic used for importing Python version specific packages

[kshitij10496]

Hey @jgonggrijp
Thank you for this package.

In this PR, I have tried to unify the import statements for Python version specific packages into a single conditional clause.

[jgonggrijp]

Thank you for your PR, @kshitij10496 (which is your given name, Kshitij or Saraogi?). It does look a bit neater this way.

With one more small change, it could look a little bit neater still. Would you mind adding another commit for that? Cheers.

[jgonggrijp]

While you're at it, to complete the neatness, would you mind moving these two lines above the if/else block? Thanks in advance.

[kshitij10496]

Thank you for your PR, @kshitij10496 (which is your given name, Kshitij or Saraogi?). It does look a bit neater this way.

I am happy to contribute. BTW, my first name is Kshitij.
I will reorder the import statements as you have suggested and squash the commits, if that works for you.

[jgonggrijp]

In this case I don't mind a squash, but in general it is better to leave history unchanged once it has been published. Do what you prefer, I'll merge it either way.

[kshitij10496]

In this case I don't mind a squash, but in general it is better to leave history unchanged once it has been published.

I couldn't agree more.
I have updated the PR. Let me know if any additional changes need to be made.

[jgonggrijp]

Oops, I almost missed this: this project uses git-flow, incidentally by the same author as the original pip-tools. Basically, this means that your branch should be merged into develop, not into master (as your PR is requesting). This is also mentioned in the CONTRIBUTING.md.

I manually merged your branch into develop. GitHub will however not recognize this as acceptance until the next release is out, when master finally descends from your contribution. So this PR will appear "open" for the time being, even though I have already accepted it.

[kshitij10496]

@jgonggrijp That's fine by me.
Thanks for the prompt review and merge.