Log file Viewer

[14:58:55] <ronny> hi jaraco

[14:59:17] <jaraco> heya ronny

[15:00:10] <jaraco> I looked at your bitbucket_issue_migration fork yesterday. Yes, I agree it’s probably not worth merging that functionality back into the root - so my thought is we’ll do the migration with your fork.

[15:30:20] <ronny> jaraco: wana wait for me to finish the username mapping, or is it not that relevan for you

[15:30:56] <ronny> (i hope i can finish this weekend, but im still on flat hunt across germany, monday i'll start at redhat)

[15:31:00] <jaraco> ronny: Your preference. Obviously, the more accurate the migration, the better… but within reason.

[15:31:52] <jaraco> Sounds good. Let’s see where you are after the weekend. Feel free to ping me here or on twitter if you want me to give it a whirl.

[15:32:09] <ronny> jaraco: my proposal would be to finish the implementation, and then have many people update the username mappitnhs, which are aslo tracked in the repo

[15:32:33] <ronny> (im also preparing to move pylib, execnet, experimenting with the pypy issue tracker for size and so on)

[15:33:08] <ronny> and i have taken syncing usermaps into account

[20:56:53] <spgingras> Just curious: what are the motivations to rewrite PyPI?

[21:03:16] <dstufft> spgingras: have you seen the legacy code base at all? ;]

[21:03:38] <spgingras> nope, I guess it's become unmaintainable?

[21:03:58] <sigmavirus24> s/become/has always been/

[21:06:07] <dstufft> spgingras: https://bitbucket.org/pypa/pypi/src/5f29d1de4c6faa1f91917cb2f1d8e6cad6e31824/webui.py?fileviewer=file-view-default

[21:06:17] <dstufft> https://bitbucket.org/pypa/pypi/src/5f29d1de4c6faa1f91917cb2f1d8e6cad6e31824/store.py?fileviewer=file-view-default

[21:07:11] <dstufft> it has no web framework (it predates all of them except zope) no testing (it predates TDD and the like) and it's code is best described as a frakenmess of random bits and pieces that have been added over a decade and a half with whatever is most expedient

[21:07:48] <spgingras> omg, I agree it's fugly

[21:08:15] <spgingras> is there a ETA for PyPI shutdown?

[21:09:16] <dstufft> Well PyPI isn't going to shut down, we'll do a live migration from one to the other with minimal disruption, but we're currently hoping for 2016Q1, but the real answer is whenever it's ready

[21:19:53] <spgingras> awesome. Is there a public roadmap for the project, other than the Github issues?

[21:34:56] <dstufft> spgingras: just the github issues really, the only thing like a roadmap besides those exists primarily in my head :/