Log file Viewer

[00:22:04] <_habnabit> dstufft, so are there plans to add a real install_requires?

[00:40:10] <jessamynsmith> dstufft: is there is a similar trick to this for test requirements? https://caremad.io/2013/07/setup-vs-requirement/

[02:15:17] <tomprince> _habnabit: Isn't that what setup_requires is? Or do you have some different idea of what a real install_requires would do.

[02:15:59] <tomprince> I know that dstufft has talked about getting pip to take over installing stuff for setup_requires.

[04:02:24] <_habnabit> tomprince, yeah, i think if pip knew how to deal with setup_requires, it would be okay. the problem with setup_requires is it's setuptools installing the crap, so it doesn't respect my pip flags

[05:58:33] <zd> Would it be possible to replace https://pypi.python.org/pypi/rawsql/0.1.0 with https://github.com/zacharydenton/rawsql ? Not sure how to contact the package owner.

[07:20:35] <ronny> moin

[19:29:56] <calston> is there some way to force pip to rebuild a package

[19:34:55] <calston> because looking for the pip cache on windows is like trying to remove stuxnet

[19:36:50] <dstufft> pip doesn't have a build cache by default, only a download cache

[20:31:27] <Ivoz> calston: pip install --force-reinstall

[20:34:00] <ronny> sup

[20:34:25] <Ivoz> hello

[20:34:29] <ronny> dstufft: are there any thoughts on having a global package repo and using symlinks into venvs to "install" to save time and space?

[20:35:10] <Ivoz> we have tb hdds and we want to save space on kbs of code?

[20:35:55] <dstufft> ronny: I've thought about it. I'm on the fence. Saving time I feel like could be better accomplished by creating a default to on wheel cache. Saving space I'm not sure if it's worth it when it means that people can't edit the files in their virtual envs anymore and have that isolated. I'm not sure how many people do that (I do sometimes) so not sure which is better

[20:36:48] <Ivoz> windows doesn't like the idea of symlinks :/

[20:55:08] <ronny> dstufft: arent they supposed to do pip install -e for editable things anyway

[20:55:32] <dstufft> ronny: yes, but sometimes I go in and edit installed stuff for debugging purposes

[20:55:33] <ronny> dstufft: i want to reach a state, where a virtualenv is bascially a bin folder and a pth file

[20:55:50] <dstufft> I do this a lot especially in temporary throw away virtual environments

[20:55:53] <ronny> dstufft: that case would need a reinstal then

[20:56:27] <ronny> dstufft: i'd mostly want to use that for tox and development venvs, i'd definitively use it as opt-in

[20:56:59] <dstufft> ronny: yes, the change in behavior is that virtual env no longer fully isolates my installation, that may be a desireable outcome, hence why I'm on the fence :)

[20:57:24] <ronny> dstufft: shared pyc cache and shared files are a bug plus

[20:57:58] <ronny> dstufft: and semantcially its still isolated, its just als non-editable (which works well in many use-cases

[20:58:31] <ronny> dstufft: for that repo, file writing would be forbidden, just as folder writing, and the filenames would aslo have a indication

[20:58:46] <ronny> dstufft: i have a rough plan, i just dont know who to cordinate

[20:59:06] <ronny> dstufft: that plan also involves eventual conda and conda env support (a friend of mine wants to work on that as soon as the base id done)

[20:59:23] <dstufft> ronny: right, and the truth is that they aren't fully isolated now (you can't edit stdlib files for instance), so it'd just be making them more "virtual" than before

[20:59:56] <dstufft> ronny: an issue or a mailing list thread is probably the best places to discuss if that's something we want to do, or a PR that makes a PoC

[21:00:14] <dstufft> ronny: there's also some other issues, like where do you store the "real" files

[21:00:14] <ronny> dstufft: actually it would give perfect isolation, anything within the venc is ediable by the user, anything outside isnt

[21:00:27] <ronny> and the shared files would be outside

[21:01:43] <ronny> dstufft: actually colocated with user-site, but allowing distros to create some kind of cache

[21:01:55] <ronny> (the idea si that distros ship and use such packages as well

[21:02:10] <ronny> i needsomeone to brainstorm this for 1-2 hours, then it can start

[21:02:57] <ronny> also afk for rl

[21:03:33] <dstufft> ronny: so it because interesting too, because one problem with that is it makes it harder to share a virtual environment between users (not impossible, but either you encode direct paths to the user dirs so that things just "work" when the dependency isn't in your user dir but is in someone elses, or everyone who uses it needs to ensure they pip install or something before using it)

[21:04:29] <ronny> dstufft: they are not exactly shareable, as of now as well, pip install is kinda mandatory

[21:04:31] <ronny> *off*