[15:47:53] <tos9> bleh I hate the words I'm about to say but is there a pep517 backend that works by just munging PYTHONPATH
[15:48:29] <tos9> I'm trying to fix a package (pytorch) that doesn't properly specify its build deps
[15:49:01] <tos9> which amongst other minor issues ships a directory alongside the main package that I would guess it wants added to PYTHONPATH in order to build a dist
[15:49:23] <tos9> I don't see it trying to do that munging itself so probably whatever their build system is does it
[15:49:52] <tos9> I could do the right thing and give that tools package a setup.py and install it normally using build_requires but I'm betting the package maintainers will go "nah that's weird"
[16:33:49] <toad_polo> tos9: You can modify sys.path in setup.py if you want.
[16:34:04] <toad_polo> That seems easier than a custom backend.
[16:35:53] <toad_polo> Or is the problem that it's not in a consistent location relative to setup.py due to build isolation or something?
[17:59:07] <pybert> If I compile this manually I get my latest update to the code, but using pip with git+ always seems to use the old version of the code
[17:59:33] <pybert> Im a little confused how I can force pip to use this specific commit hash, and not the previous one.
[17:59:58] <pybert> someone suggested there is something hardcoded in the setup.py file
[18:01:45] <pybert> but I cant see how, version=2.0.4 affects anything unless pip looks at that and looks for a version tag in the repo to override the commit tag that I specified.
[19:56:59] <ThiefMaster> shouldn't this python_requires prevent pip on python 2 from installing this particular version? https://github.com/claudep/translitcodec/blob/master/setup.py#L21
[19:57:55] <ThiefMaster> both when installing my own package that only depends on `translitcodec` without a version specification and when using `pip install` directly, i end up with the incompatible package
[19:58:57] <ThiefMaster> oh he's importing his package in setup.py.. maybe that's why it's breaking?
[20:02:24] <toad_polo> Looks like that line was added 1 hour ago.
[20:02:48] <ThiefMaster> yes, he released 0.5.1 after that (the sdist on pypi contains it as well)
[20:03:25] <toad_polo> So presumably what's happening is that `pip install theproject` ignores 0.5.1, then falls back to 0.5, which doesn't have `python_requires`.
[20:03:45] <toad_polo> Ah, though I guess that version has been yanked or otherwise removed.
[20:03:51] <ThiefMaster> yeah, he removed that version
[20:04:01] <ThiefMaster> and pip explicitly gives me 0.5.1, not 0.5.0 ;)
[20:04:07] <ThiefMaster> (in a fresh 2.7 virtualenv)
[20:04:16] <toad_polo> What version of pip are you using?
[20:04:22] <toad_polo> And are you downloading from pypi.org?
[20:05:27] <toad_polo> Note the lack of Requires-Python metadata on that page. Compare to this: https://pypi.org/project/python-dateutil/
[20:06:56] <ThiefMaster> thx, forwarded your answer to the guy: https://github.com/claudep/translitcodec/issues/3#issuecomment-576041320
[20:07:19] <toad_polo> You may also want to tell him to switch out the reference to `distutils` in `setup.py` with `setuptools`.
[20:07:38] <toad_polo> If he had a recent version of `setuptools` `setup.py upload` would have raised an error.
[20:08:19] <toad_polo> But if you don't import `setuptools` and you invoke `setup.py` directly, it uses `distutils`, which is mostly maintained using monkey-patches from setuptools :P
[20:08:52] <toad_polo> By the way, can you s/toad_polo/<whatever_you_want>/g there?