PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Wednesday the 1st of July, 2015

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[00:36:56] <dstufft> lifeless: ^^
[00:56:38] <lifeless> dstufft: so thats 'virtualenv is out' ?
[00:56:58] <dstufft> lifeless: yea
[01:30:27] <lifeless> cool
[03:15:17] <lifeless> hmm no jimbake
[03:17:01] <lifeless> hih
[03:17:02] <lifeless> huh
[03:17:04] <lifeless> https://pypi.python.org/pypi/jip
[18:11:33] <jaraco> Can someone give me admin access to github://pypa/setuptools_scm? I don’t have access to rename/delete the repository, which is necessary for migrating the issues from bitbucket, something which I’ve been keeping Ronny apprised.
[18:12:01] <jaraco> I probably actually need admin access to /pypa in order to transfer ownership of /jaraco/setuptools_scm to /pypa
[18:33:07] <dstufft> jaraco: um, I think so
[18:34:05] <dstufft> jaraco: gave you admin to pypa/setuptools_scm
[18:34:11] <dstufft> that should let you transfer in too
[18:34:17] <jaraco> dstufft: Great. Thanks.
[18:34:32] <dstufft> jaraco: any cahnce we'll be getting setuptools on github too? :D
[18:35:06] <jaraco> Maybe. It’s got a complex history and a lot more tickets.
[18:36:17] <jaraco> I signed out and back in, but i still don’t have a settings button for /pypa/setuptools (github)
[18:36:22] <jaraco> sorry
[18:36:34] <jaraco> /pypa/setuptools_scm
[18:37:24] <dstufft> jaraco: did you check your email
[18:38:28] <dstufft> jaraco: not that my opinion matters that much, but I would be super happy if setuptools was on github :)
[18:38:43] <jaraco> I see
[18:39:14] <dstufft> I see you accepted the invite, do you have the settings button now?
[18:40:54] <jaraco> I do!
[18:40:56] <jaraco> !thanks dstufft
[18:40:57] <pmxbot> you're doing good work, dstufft!
[18:41:03] <dstufft> awesome
[18:41:07] <dstufft> let me know if you need more
[19:50:32] <lifeless> jaraco: would it help if someone else did the migration for you ? Like - is it time or interest that is needed ?
[20:32:12] <jaraco> lifeless: it’s more a matter of unknowns - what will break, whom to inform, etc. It just seems to be to be a substantial effort for a small win (and some loss) while there are dozens of more important tickets to address. Personally, I’m happy with Mercurial too. Is there a consensus that pypa projects should be in github?
[20:34:52] <dstufft> jaraco: there's not a requirement or anything, just most of them are there :) The ones on hg are setuptools, wheel, pypi, bandersnatch, setuptools_scm, setuptools_scm is moving, pypi is dead once Warehouse (which is on github), so that leaves setuptools/wheel/bandersnatch
[20:50:23] <lifeless> jaraco: I don't have a view. I will use whatever folk need
[20:51:09] <lifeless> jaraco: I was merely going to offer some ergs towards the thing if it was desired because a reduction of friction is something I generally support - even though I'm not advocating a particular direction here
[22:10:51] <dstufft> lifeless: heh, just personally had a use for -c
[22:27:13] <lifeless> dstufft: HAHAHAHA :)
[22:27:27] <lifeless> dstufft: sorry, I'm glad to see it was useful. Now, about choose-lowest ? :)
[22:31:21] <dstufft> lifeless: I was thinking about that a bit. I'm warming to the idea a bit, though I'm waffling back and forth a bit if it would be better as a --choose-lowest option, or if it would be better to make the thing that picks what version to install pluggable (but I don't know how that would interact with future efforts to add a better dep solver, so I'm not sure)
[22:32:28] <dstufft> my kingdom for a requirements.txt.lock :/
[22:34:25] <lifeless> pluggable would be trickier
[22:34:28] <lifeless> but I can see the appeal
[22:36:26] <dstufft> I'm not sure that it's worth the effort to do pluggable
[23:26:44] <jaraco> ronny, et al, the migration from bitbucket is complete. I’ve e-mailed ronny the details of the issues that were lost from github. We can restore those manually if necessary. It might be necessary to restore the travis-ci integration also.
[23:28:05] <jaraco> I’ve subsequently disabled the issue tracker in bitbucket again.