Log file Viewer

[15:11:21] <sumanah> toad_polo: hey I saw your question in http://kafka.dcpython.org/day/pypa/2018-03-24

[15:11:45] <sumanah> toad_polo: a contributor added info in https://github.com/pypa/python-packaging-user-guide/pull/457

[15:11:59] <sumanah> to https://packaging.python.org/tutorials/distributing-packages/

[15:23:07] <toad_polo> sumanah: Ah good to know. Assuming the license is compatible, might be a good idea to see if we can get some of that added to the setuptools documentation as well. There's an open issue for it there: https://github.com/pypa/setuptools/issues/1236

[15:32:45] <sumanah> toad_polo: back in a moment, but, yeah, that sounds good

[16:01:35] <sumanah> pypi.org is now in beta. https://wiki.python.org/psf/WarehouseRoadmap https://pyfound.blogspot.com/2018/03/warehouse-all-new-pypi-is-now-in-beta.html

[19:53:29] <sumanah> I have just sent the inaugural pypi-announce email https://mail.python.org/mm3/archives/list/pypi-announce@python.org/thread/PCR7EEVLDOCV35LEPMQQ7JOFQCGARMZR/

[20:54:28] <wsanchez> Howdy PyPA. Before I go hacking with my machete, is there a supported/recommended way to generate source code prior to or within sdist? (My specific use case is .proto file -> .py file.)

[20:55:31] <ngoldbaum> could subclass setuptools.command.sdist and your own implementation of the run function

[20:55:43] <ngoldbaum> that calls run on the superclass once you're done generating code

[20:56:27] <wsanchez> OK, and how to I register this subclass as the one to use?

[20:56:54] <ngoldbaum> the cmdclass argument to setup()

[20:57:16] <ngoldbaum> setup(..., cmdclass={'sdist': my_sdist}, ...)

[20:57:51] <wsanchez> OK I'll give that a spin, thanks

[21:18:11] <mar77i> hi, how can I install psycopg2 with pip, so it's actually compiled? http://initd.org/psycopg/docs/install.html#install-from-source

[21:19:03] <ngoldbaum> you mean so you don't get the wheels from pypi?

[21:19:49] <mar77i> just to be on the same page, what exactly is a wheel? a built, ready to use ball of some sorts?

[21:20:03] <ngoldbaum> it's a binary package format that python packages use

[21:20:16] <ngoldbaum> all the .whl files in the file listing

[21:20:17] <ngoldbaum> https://pypi.python.org/pypi/psycopg2

[21:22:16] <mar77i> hmm. so pip only installs these ready-built things?

[21:22:54] <mar77i> s/things/wheels/

[21:22:56] <ngoldbaum> no

[21:23:02] <ngoldbaum> it installs a wheel if it's available

[21:23:14] <ngoldbaum> but if not it will try to build a wheel using the source distribution

[21:23:38] <ngoldbaum> you can tell pip to ignore wheels like this:

[21:23:40] <mar77i> I'm getting this nasty warning and tried reinstalling the package a few times already, but I can't seem to not use the wheel that ships this ugly warning.

[21:23:52] <ngoldbaum> pip install <package> --no-binary :all:

[21:24:49] <mar77i> hmm. okay. and there doesn't happen to be just the ideal way to add these args in the requirements file?

[21:25:32] <ngoldbaum> i don't know if there's a way to encode that in a requirements file

[21:26:29] <ngoldbaum> ah, apparently you can

[21:26:33] <ngoldbaum> https://github.com/pypa/pip/issues/3469

[21:48:22] <mar77i> this ... didn't solve the issue.

[21:50:18] <sumanah> mar77i: we (the makers of PyPI) are also running into the warning

[21:54:26] <mar77i> I was going for the promised remedy, though, by setting `--no-binary all` in requirements.txt and it seems ... I forgot to set PATH, though. http://initd.org/psycopg/docs/install.html#install-from-source

[22:16:38] <ngoldbaum> mar77i: --no-binary :all:

[22:16:40] <ngoldbaum> not all

[22:21:00] <mar77i> ah wait, that also counts for when writing the args to the same line?

[22:21:28] <mar77i> trying it...

[22:27:55] <mar77i> yay, it worked. the message is gone. thanks everyone. :)

[23:30:32] <njs> mar77i: the confusing thing here is that --no-binary also lets you say specific packages that you want to use source for, e.g. --no-binary psycopg2. So if you just write '--no-binary all', the pip thinks that means that when you're installing the package named 'all', you don't want to use the binary.

[23:31:02] <njs> mar77i: so that's why they came up with the funny ':all:' thing -- you can't have colons in a package name, so that's unambiguously a special marker