Log file Viewer

[07:20:42] <d0ugal> Any idea why this doesn't show up when searching "mistral" on PyPI? https://pypi.python.org/pypi/mistral

[07:20:49] <d0ugal> https://pypi.python.org/pypi?%3Aaction=search&term=mistral&submit=search

[09:15:34] <FRidh> rebuilding nixos against master (d15fedb) and for some reason I have to build Qt4. Is this the Skype issue again?

[09:15:44] <FRidh> oops, wrong channel :)

[09:51:27] <[Tritium]> d0ugal: searching on pypi.python.org is kinda broken. try searching pypi.io

[10:26:27] <d0ugal> [Tritium]: Thanks, I didn't know about that project.

[10:27:07] <[Tritium]> d0ugal: its the next implementation of pypi, just on its own domain

[10:27:38] <d0ugal> [Tritium]: So it is, last time I looked it was warehouse.python.org, but I see that redirects now.

[11:59:48] <dowwie> dstufft: woah. " 293.1TB of bandwidth serving 3 billion HTTP requests during the month of April 2016 alone"

[12:02:25] <dstufft> dowwie: yea :] PyPI pushes some numbers. It's quite exciting to work on it to be honest, the numbers (while certainly not google scale or anything) never cease to make me go "wow"

[12:03:27] <dowwie> dstufft: and by feats of engineering and lots of duct tape manages to make it all happen

[12:11:44] <mvantellingen> dstufft: i might be able to help out with warehouse on and off, is there a list with easy pickings or should I just submit some pr's?

[12:13:50] <dstufft> mvantellingen: there are a few issues tagged "easy", but honestly we're not super great at categorizing between "easy" and "not easy". The "Launch" milestone has the issues deemed most important for being able to actually launch, but you don't have to limit yourself to those things either. Really whatever you want to work on is totally fine :)

[12:17:47] <mvantellingen> ok, I'll see what I can do. :-)

[12:20:02] <dstufft> mvantellingen: sounds great :) If you run into any problems don't hesitate to shout (though I'll be unavailable for part of today, if you're planning on working on it today)

[12:20:44] <mvantellingen> I'll try to get it up and running locally, and make me familiar with the codebase first. Have some experience with pypi servers (localshop)

[12:31:54] <dstufft> mvantellingen: cool :) If you're familar with docker and docker-compose at all, it's setup to run easily inside of that for development

[12:32:20] <[Tritium]> dstufft: will warehouse live at pypi.python.org when launched or will it stay at pypi.io?

[12:32:52] <dstufft> [Tritium]: It will stay at pypi.io, and pypi.python.org will redirect

[12:32:56] <dstufft> To insolate it from everything that runs on the *.python.org domain name

[12:32:59] <dstufft> isolate*

[12:33:06] <dstufft> sort of combined insulate and isolate there

[12:33:53] <[Tritium]> i can sort of see that being a source of short term pain

[12:34:16] <dstufft> which part?

[12:34:47] <[Tritium]> the redirect. I'm sure pip will do the right thing, of course. It's other tools or workflows...

[12:35:15] <[Tritium]> Then again.. https://xkcd.com/1172/

[12:35:33] <dstufft> (I know one part that will be somewhat painful - uploading which can't follow a redirect, but I'm working to get upload.pypi.io ready before warehouse itself is ready so I can start directing people to use it instead, get twine updated, work with downstream redistributors to get their Pythons and stuff updated to point to the new location)

[12:36:25] <[Tritium]> ... the launch of pypi.io might actually force a point update to 2.7

[12:36:43] <dstufft> heh

[12:36:49] <dstufft> that would be kind of awesome t b h

[12:37:11] <[Tritium]> pypi.python.org is baked into distutils, i think

[12:37:24] <dstufft> yea it is

[12:37:35] <[Tritium]> ... should I bring that up on python-dev?

[12:37:47] <dstufft> Barry Warsaw suggests that it shouldn't be a problem to update Debian to the new URL

[12:38:08] <dstufft> I haven't talked to other down streams yet

[12:38:34] <dstufft> [Tritium]: eh, I don't know that it matters much. I have commit bit on CPython so once upload.pypi.io is ready I can just go and change the URL

[12:38:37] <[Tritium]> Im not too worried about the distros... or even homebrew... its the windows side that get vanilla python

[12:39:06] <dstufft> there'll be an error message telling you what to do as well

[12:39:10] <[Tritium]> aye

[12:39:17] <dstufft> You can modify where distutils uploads via ~/.pypirc

[12:39:23] <dstufft> so it doesn't _require_ a new Python

[12:39:45] <[Tritium]> it would just be another thing fixed in a 2.7.12

[12:39:52] <dstufft> yea

[12:40:12] <dstufft> and might push more people over to twine, which is a generally good thing IMO

[12:40:16] <[Tritium]> and the same would apply to 3.3-3.5.2

[12:41:07] <[Tritium]> ...there was something that twine couldnt do, but i cant remember what it was

[12:41:15] <[Tritium]> login i think?

[12:41:16] <dstufft> register?

[12:41:25] <[Tritium]> register might be it

[12:41:35] <dstufft> For awhile twine couldn't register, which didn't matter a whole lot except for new projects

[12:42:02] <dstufft> since PyPI auto registers for anything but brand new

[12:42:13] <[Tritium]> yeah

[12:42:14] <dstufft> but Ian added ``twine register``

[12:42:20] <Wooble> honestly I'd register a new project through the web interface before I even had a setup.py just so I know I have the name before I write something releasable...

[12:43:01] <Wooble> some projects might not bother searching to see their name's available first *cough*mypy*cough*

[12:43:07] <[Tritium]> ...I should update my firefox pypi search plugin

[12:43:20] <[Tritium]> what a horrible name for a project, too

[13:24:27] <[Tritium]> it kinda feels dirty that building warehouse requires node

[13:27:44] <dstufft> [Tritium]: heh, that's for the front end stuff :]

[13:27:57] <dstufft> it's hard to use anything reasonable modern front end wise that isn't tied to node

[13:28:01] <dstufft> reasonably*

[13:28:08] <[Tritium]> ...so it doesnt require node as much as it requires npm?

[13:29:00] <dstufft> [Tritium]: Well, it uses Gulp to compile the static assets, which is JS

[13:29:06] <[Tritium]> ahh

[13:29:14] <dstufft> along with babel to transpile from es6 syntax to es5

[13:29:39] <[Tritium]> its...cringeworthy watching it manually invoke setup.py install to install things

[13:30:22] <dstufft> Warehouse? It shouldn't manually invoke setup.py, that's all pip

[13:31:11] <[Tritium]> oh that is pip. that is not the output of pip i am used to

[13:34:28] <dstufft> Yea, it's a bit janky, it's the "we don't have a tty so we can't do fancy graphics" mode of pip

[13:46:37] <Wooble> What, no eating pyjs dogfood? ;)

[13:53:16] <[Tritium]> ... the security page of current pypi suggests using ssh to upload...

[13:53:24] <[Tritium]> i ...didnt know that was a thing

[13:53:52] <[Tritium]> and apparently it isnt

[13:55:01] <wleslie> hello. what is the best way to have a wheel include the .so that I'm wrapping? is that a bad idea?

[13:55:55] <[Tritium]> wleslie: ...manylinux1 or something internal?

[13:56:12] <wleslie> manylinux1

[13:56:35] <wleslie> by which I mean I haven't checked, this so just doesn't have many deps

[13:56:56] <[Tritium]> >.> if you are going through the trouble to use manylinux you might aswell statically link it

[13:57:52] <wleslie> that means I've got to figure how to do so with cffi

[13:59:25] <[Tritium]> auditwheel has facilities for this, apprently

[14:14:13] <wleslie> ok, that wasn't too hard.

[14:26:28] <dstufft> [Tritium]: it was a thing for awhile, before we had TLS for PyPI that could be validated

[14:27:09] <dstufft> we killed it in 2013 when we migrated from a single host on OSUOSL to many web nodes, because the implementation didn't work out well for scaling out horozontally

[23:55:42] <pjs> Hey all.. Trying to upload a new version of a couple of packages I have on pypi and am getting this when trying to register: Server response (400): Invalid URI: u'UNKNOWN'

[23:56:15] <pjs> It's an existing pacakge. I've never seen this before. Is there anything going on?