Log file Viewer

[00:21:06] <tdsmith> for the life of me i can't find an easy way to reproduce the setuptools weirdness i found this morning

[00:21:22] <tdsmith> it happens consistently through homebrew but i can't figure out why

[00:49:36] <goodwill> so it looks like new virtualenv/pip won't work on Ubuntu 12.04 cause of the SNIWarningError

[00:55:23] <agronholm> goodwill: not sure what ubuntu has to do with it as this is about jython

[00:55:41] <agronholm> jython 2.7.1 will already fix that InsecurePlatformWarning, not sure about the SNIMissingWarning

[00:55:42] <goodwill> agronholm: erm, what?

[00:55:54] <agronholm> goodwill: that paste was made with jython

[00:55:59] <goodwill> agronholm: what paste?

[00:56:08] <goodwill> agronholm: I did not do any paste

[00:56:13] <agronholm> ah, you joined afterwards

[00:56:18] <agronholm> <[Tritium]> so this is weird... http://paste.pound-python.org/show/CKiGooRUA5gHMr8DP6SY/

[00:56:23] <agronholm> I thought you were referring to this

[00:56:26] <goodwill> nah

[00:56:31] <goodwill> so weird

[00:56:32] <goodwill> now it work

[00:56:37] <goodwill> I wonder what happened

[15:12:53] <adourado> Hey, I'm looking into how to setup a private PyPI server at work, and I'm a little confused on what the official package is, there's seems to be at least three or four pypi server packages on pypi.python.org. Can anyone point me in the right direction regarding the recommended way of doing this?

[15:25:37] <vichak> hello

[15:26:29] <vichak> is Warehouse ready for production? I only see development environment set up in documentation.

[15:27:46] <dstufft> adourado: you probably want something like devpi

[15:28:21] <dstufft> The code that powers PyPI itself (both Legacy PyPI, and Warehouse) is not really intended to be used anywhere except for PyPI itself

[15:30:28] <vichak> ok thanks

[15:32:57] <adourado> dstufft: is this a package?

[15:33:14] <dstufft> https://pypi.python.org/pypi/devpi

[15:38:52] <elarson> there are a ton of pypi index projects and it is tough to know what is a good one to look too

[15:39:14] <adourado> that's exactly my dilema

[15:40:57] <elarson> adourado: other than getting used to it, devpi has been really nice

[15:42:01] <adourado> elarson: good to know. And it's basically the same thing as PyPI, right? I can install stuff with pip, and mix official packages with the ones in devpi?

[15:44:32] <dstufft> yes

[15:44:43] <dstufft> it doesn't take much to be compatible with pip

[15:44:48] <dstufft> we purposely make it very easy :[

[15:44:50] <dstufft> :] *

[15:46:59] <elarson> adourado: the only gotcha I've found has been the ACL bits, but I'm still very new to it.

[15:47:09] <adourado> Cool. It seems precisely what I need. The fail over to PyPI is specially cool, we might not even need to tell people to configure their requirements.txt properly to install from different servers

[15:47:41] <elarson> getting it up and running with nginx was reasonably easy. I even got ssl termination and http basic auth in place, which was a first for me

[15:47:53] <adourado> I don't think we'll be needing ACL, the stuff we wanna host is used everywhere in the company

[15:48:11] <elarson> adourado: well you still have to have a user and that user has a repo

[15:48:57] <elarson> this is actually a good thing b/c you can have things like staging/prod repos or whatever else to help a pkg go through some ci workflow

[15:49:44] <elarson> adourado: for example, I'm only using a $project/pypi repo where the "user" is the $project

[15:50:04] <adourado> hmm

[15:52:08] <adourado> can I block people from creating users for themselves?

[15:52:38] <adourado> Ideally, only a couple of devs would be able to do it, and everyone one else would just download from us

[15:55:31] <elarson> adourado: yes, the user creation is explicitly done by the devpi client

[15:56:06] <adourado> but anyone with the client can do it? If I don't use the --restrict-modify thing?

[15:58:48] <elarson> adourado: I'd check the docs. I put nginx in front with http basic auth to prevent it from being wide open.

[15:59:44] <adourado> but then users have to configure pip properly to authenticate

[16:00:13] <adourado> and some of our users are ... avert to change, to put it mildly

[16:00:59] <elarson> adourado: yes, that is true. we deploy those creds via config management to the hosts for that aspect

[16:01:13] <elarson> and then ci pushes packages

[16:01:39] <elarson> but that is just us. you can probably restrict it via the firewall or a proxy or anything really

[16:01:45] <elarson> or don't! leave it wide open :)

[16:02:54] <adourado> We already have internal DNS and firewalls in place, I guess, most of the internal stuff is running in http, for instance

[16:04:12] <adourado> IT security seems to assume there're no malicious agents inside the company, and none can get into the network

[16:04:43] <elarson> well there you go :)

[16:05:36] <elarson> btw, there is also a pkg to allow devpi to be configured wide open, but you have to auth with nginx where it'll forward the user along so you get some user tracking on the devpi side, but without having to mess with a bunch of creds / acls

[16:08:18] <adourado> Well, the issue to setup all this is with me for now, so, as long as it stays that way, I can take some time to get everything right

[16:08:56] <adourado> Lets just hope it doesn't get assigned so "some other people" around here

[16:08:58] <adourado> >_>

[16:09:02] <adourado> <_<

[16:10:50] <elarson> config management is your friend!

[16:12:33] <elarson> that friend, when you were kids, you didn't *really* want to hang out with, but they had cool toys and let you watch R rated movies

[16:56:21] <dolley> Hi everyone, I'm looking to embed django within my project with pip3 install --target path/to/project django. But I get the error: "DistutilsOptionError: can't combine user with prefix, exec_prefix/home, or install_(plat)base"

[17:34:26] <[Tritium]> https://bpaste.net/show/70268795a0f0 I dont know if this is a virtualenv issue or an issue with the windows python 2.7 installer

[19:10:16] <dolley> Hi everyone, I'm trying to install django using pip3 in a specific directory. My command is this: pip3 install --editable /home/dolley/EO_site/EO_site/Django-1.9.1 --target /home/dolley/EO_site/EO_site/ But I get the error "option --home not recognized"

[19:10:22] <dolley> Any suggestions?

[19:17:39] <Ivo> use = instead of space between --target and /home

[19:17:52] <Ivo> dolley: I strongly suggest you try using a virtualenv to install django

[19:18:49] <Ivo> sudo apt-get install python-virtualenv

[19:19:02] <Ivo> if you're on a debian-like

[19:19:21] <Ivo> then you can run $ virtualenv -p python3 env

[19:19:36] <Ivo> $ source ./env/bin/activate

[19:19:53] <Ivo> and then simply pip install <blah, editable, etc>

[19:19:59] <Ivo> but you won't need --target anymore

[19:20:54] <jonafato> if you're on 3.5, a similar tool called pyvenv is bundled with your installation and should be already available

[20:14:27] <dolley> Ivo: thanks! (sorry, i stepped away) The purpose is this is to be include django in the app because my apache VM (and eventually production server) dont support django 1.9.1

[20:15:09] <Ivo> what do you mean "don't support django 1.9.1"

[20:15:19] <Ivo> apache is a http server, not a python interpreter

[20:20:18] <linovia> Ivo: I assume its provider doesn't have it system wide already

[20:21:03] <linovia> I second the advice, use a virtualenvenv / pyvenv

[20:23:07] <dolley> thank you Ivo and linovia!

[20:24:03] <Ivo> dolley: https://packaging.python.org/en/latest/installing/#creating-virtual-environments

[21:32:36] <dodobrain> hi all

[21:33:45] <dodobrain> i'm trying to install a package from a tarball. `pip install filename.tar.gz` works fine from a prompt in bash while it fails when run from within a bash script with this error: https://gist.github.com/anonymous/e7f3f680f5dc6aa4b78f

[21:34:00] <dodobrain> pip and setuptools are the only things installed in site-packages

[21:41:21] <karlpinc> I'm running a box with virtualenvs that have pip-tools==0.3.6 and a cron job invoking pip-review. But pip-review does not seem to be in the new pip-tools. What's the right replacement, pip list -o?

[21:42:44] <karlpinc> I'm inheriting this setup. Anything I need to watch out for doing such a replacment? (For some reason I see setuptools in the pip list -o output, but not in pip-review, although it may have to do with the way I'm invoking it v.s. the cronjob.)

[22:11:55] <ngoldbaum> OH: "Mind, I'd give it a try if pypi weren't an irreversible machine of doom"

[22:22:50] <tdsmith> sounds like they want the pypi test server

[22:24:15] <tdsmith> dodobrain: have you tried a newer pip?

[22:43:31] <karlpinc> Humm. pip 1.4.1 The -f option does not seem to recognize .egg files. Is there something I'm doing wrong or is this expected?

[23:10:35] <dodobrain> tdsmith, yeah. thanks it worked.. but i'm not 100% sure if it was just a pip issue.. i made some changes to the bash script itself.

[23:10:40] <dodobrain> anyway, problem resolved. thanks

[23:14:31] <dstufft> karlpinc: pip doesn't support .egg files