Log file Viewer

[00:05:13] <janw313_> hi! would like to contribute a patch to https://pypi.python.org/pypi/ctypeslib. but, sole developer of that project no longer has pypi access, nor has access to svn.python.org where code is hosted. any way out of that dilemma?

[01:15:49] <ionelmc> janw313_: you could ask to take over the package here http://sourceforge.net/p/pypi/support-requests/ or here https://bitbucket.org/pypa/pypi/issues

[01:16:15] <ionelmc> i'm not sure the admins do that anymore

[01:16:33] <ionelmc> janw313_: what if you make a ctypeslib2 package?

[01:21:17] <janw313_> ionelmc: thx! looks like takeover/access requests were possible two months ago ('apns-client' https://sourceforge.net/p/pypi/support-requests/549/). i will try that.

[01:22:41] <janw313_> ctypeslib2... well... my bugfix is too minor for making a new package

[01:34:21] <ionelmc> janw313_: it's not like ctypelib has any releases on pypi

[01:34:37] <ionelmc> doubt anyone uses that

[01:35:21] <ionelmc> that - the pypi package i mean, it would only work with easy_install

[15:24:22] <elarson> I'm trying to use devpi as a private repo and using a u:p in the URL fails with python setup.py upload -r my-priv-repo b/c httplib is thinking it is a port.

[15:24:45] <elarson> is there a better way to submit a package to a pypi instance that is behind http basic?

[15:25:04] <xafer> elarson you could try https://pypi.python.org/pypi/twine/ as a workaround

[15:25:39] <elarson> xafer: I'll give that a go

[15:31:43] <elarson> well twine didn't seem to complain, but I don't see the package. I'll keep poking around

[15:31:47] <elarson> xafer: thanks!

[15:33:25] <xafer> you're welcome :) make sure to put your index int the url (something like https://pypi.private.url/root/production/)

[15:34:09] <elarson> xafer: already did it :)

[15:34:41] <xafer> you put devpi behind an nginx with basic auth ?

[15:35:07] <elarson> xafer: yeah

[15:35:17] <elarson> and https

[15:36:29] <xafer> Same here, I've come up with https://github.com/Polyconseil/devpi-remote_user

[15:38:15] <xafer> with and "acl_upload=:remote_user " on the repository

[15:48:06] <elarson> xafer: what is the benefit then? does nginx send REMOTE_USER so you can reuse the auth?

[15:48:15] <xafer> yup

[15:48:48] <xafer> and there is no auth in devpi

[15:48:57] <elarson> ah ok

[15:49:34] <elarson> xafer: but a user can still do the normal bits as far as creating repos b/c it has the remote user passed through right?

[15:50:07] <xafer> I didnt try that,

[15:50:54] <xafer> I usually ssh/ansible to the devpi server to perform maintenance action like updating/creating repos and such

[15:51:30] <xafer> But register, upload and dowload work for all the users

[15:52:46] <elarson> xafer: got it. that could definitely be helpful then. thanks for passing that along!

[15:53:11] <xafer> feedback welcome ;)

[15:54:02] <elarson> as an aside, how long have you been using devpi as a private pypi? I've used chishop (I think?) before but it wasn't really "operated". devpi seemed simple and I'm a fan of pytest, so my decision was somewhat ad-hoc

[15:54:46] <xafer> since august 2015 I'd say according to https://github.com/Polyconseil/devpi-remote_user ^^

[15:55:17] <elarson> that is what I suspected :)