setup.py imports SPARQLWrapper before install_requires can be run

[cottrell]

Not a huge deal but everyone will hit this if they import mods specified in install_requires I think.

See note here:

#86

[dayures]

@cottrell What do you think to use something like https://gist.github.com/techtonik/4066623 in order to remove the import ?

[cottrell]

Seems reasonable ... Doing this kind of thing is really just trying to hook into a convention as far as I can tell. If there is some way of changing the convention to make this stuff easier that might be better. Whatever is easiest and simplest and doesn't confuse future people too much.

…

On Fri, May 25, 2018, 10:29 dayures ***@***.***> wrote: @cottrell <https://github.com/cottrell> What do you think to use something like https://gist.github.com/techtonik/4066623 in order to remove the import? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#113 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANoLLF2qzJanexSFjFK-N9jLAbrfszmks5t18D2gaJpZM4UGHmN> .

[dayures]

@cottrell maybe there are better solutions, but I didn't find them. Do you have any suggestion?

[cottrell]

@dayures #115

[dayures]

from PEP 396 -- Module Version Numbers specification:

The version attribute in a classic distutils setup.py file, or the PEP 345 Version metadata field SHOULD be derived from the version field, or vice versa.