[13:24:14] <c1b3r> I was wondering if one of you have the next problems:
[13:25:14] <c1b3r> The directory '/home/masterbrain/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
[13:25:18] <c1b3r> The directory '/home/masterbrain/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
[13:25:41] <mgedmin> that's not a problem, that's a warning
[13:26:23] <mgedmin> ok, this is getting interesting
[13:26:30] <c1b3r> the thing is that after i activate the virtualenv
[13:26:54] <mgedmin> can you pastebin the command you're running, its full output, and the output of ls -ld ~ ~/.cache ~/.cache/pip ~/.cache/pip/http ?
[13:27:18] <c1b3r> I can't do pip install anypackage
[13:54:38] <c1b3r> what would be the best to use virtualenv in production ?
[13:55:38] <Wooble> just create the venvs with a normal user account. There's no reason to use root.
[13:55:58] <Wooble> sudo pip install is only "useful" to install to the system python, which is a horrible idea.
[13:56:48] <Wooble> (use distro packages if you need to install things to the system python, although ideally forget your OS even comes with a python and leave it alone to handle system things)
[20:48:58] <_matix> Hi guys, just wondering why dependency links are being removed from setuptools / pip and what is the alternative? I have a private package that depends on another private package. i've been told to run a private pypi repository but this seems like overkill.
[20:52:59] <_matix> to clarify, I have an application App which depends on a private package PackageA. PackageA depends on private package PackageB. Everything is hosted in private Git repositories. App currently has PackageA and PackageB in its requirements.txt to cope with my issue, but it really only depends on PackageA.
[21:26:11] <nanonyme> _matix, FWIW providing a server that implements the simple interface is not *that* hard
[22:10:53] <pombreda> _matix: you could also vendor you wheels. This is quite simpler if you only have a few repos
[22:12:47] <pombreda> This is my preferred approach :) until you start reaching a larger scale (as in large number of third-parties) where having also a pupi repo may help