PMXBOT Log file Viewer

Help | Karma | Search:

#pypa logs for Thursday the 22nd of October, 2015

(Back to #pypa overview) (Back to channel listing) (Animate logs)
[07:57:51] <rnix_> good morning. i have a package with cythonized modules, and only want to include the compiled .so files to the packaged egg/wheel. i cannot find some documentation how to do this properly, maybe i just search for the wrong things. may someone point me the right direction please?
[14:02:44] <rZ_> hello all; is it possible to have a wheel name that works for any python version (universal), but only a specific OS (since the wheel contains binaries)?
[14:03:39] <mgedmin> I think so
[14:03:53] <mgedmin> e.g. .py2.py3-none-linux_x86_64.whl
[14:05:12] <rZ_> i have a .py2.py3-none-macosx.whl uploaded at https://pypi.python.org/pypi/airship-steamcloud/1.4.3 but when i install the package on a mac it installs the 'any' package
[14:05:33] <dstufft> I don't think "macosx" is a valid tag
[14:06:22] <dstufft> https://bpaste.net/show/e052947f8d92
[14:06:22] <rZ_> where would i find the tags for the different versions of os x
[14:06:25] <dstufft> that's what I get on my OSX
[14:06:34] <dstufft> note: that's SDK version *not* OSX version
[14:06:59] <mgedmin> https://www.python.org/dev/peps/pep-0425/#platform-tag
[14:07:40] <rZ_> so do i just do macosx_10_{6-11}_universal?
[14:08:09] <mgedmin> that pep could do with some more examples
[14:09:38] <dstufft> rZ_: it depends on how you compiled it
[14:10:09] <dstufft> that is describing the binary compatibility basically
[14:10:10] <rZ_> compiled what? the i didn't compile the binaries, they're redists, and they work on all versions above 10.6
[14:10:32] <dstufft> rZ_: https://en.wikipedia.org/wiki/Universal_binary
[14:10:37] <dstufft> that's what the universal stands for
[14:10:39] <rZ_> the os x ones are universal
[14:11:34] <dstufft> if it was compiled with the 10.6 SDK and it's a universal binary, then you only need macosx_10_6_universal then
[14:11:40] <rZ_> ah. okay
[14:12:01] <rZ_> while i'm here are the win32 and win64 tags valid?
[14:13:01] <dstufft> I don't have a windows computer to check but I *think* they are just win32 and win_amd64 (and probably another one for itanthum)
[14:14:15] <rZ_> okay, i'll have to check later
[14:14:16] <rZ_> thank you
[14:15:18] <rZ_> actually wait, pip is still installing the wheel tagged 'any', is this a correct wheel? "airship_steamcloud-1.4.8-py2.py3-none-macosx_10_6_universal.whl"
[14:17:48] <dstufft> rZ_: what version of pip
[14:18:00] <rZ_> 7.1.2
[14:18:28] <rZ_> setuptools is out of date and i'm on 10.11 if that makes a difference
[14:20:21] <dstufft> hm
[14:20:22] <dstufft> sec
[14:21:43] <dstufft> oh
[14:21:44] <dstufft> I see
[14:22:09] <dstufft> rZ_: it looks like we don't currently generate the proper platform tags for all of the pyN versions
[14:22:21] <dstufft> ('py3', 'none', 'macosx_10_11_universal') is all we generate
[14:22:31] <dstufft> we should fix that
[14:22:55] <rZ_> so i don't have to change anything and i just have to wait for that to be changed?
[14:24:47] <mgedmin> why does 'pip uninstall' perform HTTP requests after removing the package files?
[14:25:04] <mgedmin> just saw an InsecurePlatformWarning from urllib3 at the end of the command output
[14:26:26] <dstufft> mgedmin: any execution of pip pings PyPI to check if you're running the latest version of pip (with the modulo that the result to that is cached for a week, so it's once per week per virtualenv or user)
[14:26:41] <dstufft> rZ_: yea, unless you want it to work in the meantime
[14:27:09] <rZ_> if it'll work at some point then that's fine, i'm okay with downloading the any wheel
[14:28:46] <dstufft> rZ_: https://github.com/pypa/pip/issues/3202
[14:29:01] <rZ_> thanks
[14:51:38] <rZ_> not exactly pypa related but i'm trying to work with the creator of the scandir package (os.scandir() in 3.5) to improve compatibility with non-CPython interpreters as well as 3.2.x
[14:52:03] <rZ_> i have a PR open but they haven't had any time to look at it and they say they need to test it in more environments
[14:52:09] <rZ_> so i was wondering if someone could help them out
[14:54:22] <rZ_> https://github.com/benhoyt/scandir/pull/53d
[14:54:26] <rZ_> https://github.com/benhoyt/scandir/pull/53 *
[18:48:02] <jaraco> I see that support requests for pypi seem to have been locked - https://sourceforge.net/p/pypi/support-requests/510/
[18:48:10] <jaraco> That returns a 403 Read access required.
[18:50:22] <jaraco> Odd that it seems that only that request was marked as such.
[18:51:12] <jaraco> Perhaps a password was unintentionally disclosed, so that ticket was marked as private.
[18:51:18] <jaraco> Reason I ask is this - https://github.com/cburgmer/upsidedown/issues/6
[18:53:09] <jaraco> Any idea why that request is hidden?
[19:35:05] <dstufft> jaraco: um
[19:35:07] <dstufft> jaraco: no idea
[19:35:11] <dstufft> let me see if I have access to it
[19:35:58] <dstufft> jaraco: looks like Richard marked it private because he asked for an email address on it
[19:46:20] <jaraco> makes sense.
[19:46:22] <jaraco> !thanks dstufft
[19:46:22] <pmxbot> you're doing good work, dstufft!
[20:45:15] <consfearacy> hello
[20:45:20] <consfearacy> can anyone help me with upgrading pip?
[20:45:43] <consfearacy> in slackware I do this:
[20:45:51] <consfearacy> 'sboupgrade pip'
[20:45:56] <consfearacy> it first tells me: pip is complementary with virtualenv, and it is encouraged that you use
[20:45:59] <consfearacy> virtualenv to isolate your installation.
[20:46:08] <consfearacy> and then when i continue the upgrade it gives me an error:
[20:46:21] <consfearacy> ImportError: No module named setuptools
[20:46:21] <consfearacy> Failures: pip: pip.SlackBuild return non-zero
[20:46:37] <consfearacy> setup.py line 6, it says
[20:46:40] <consfearacy> any help?
[20:46:47] <consfearacy> pip 7.1.2
[20:47:48] <mgedmin> sounds like a very slackware-specific question to me
[20:47:51] <mgedmin> is there a #slackware?
[20:48:28] <consfearacy> yes there is
[20:48:37] <consfearacy> ok then i ask you another question
[20:48:47] <consfearacy> one time i made the mistake of installing python3 while i already had python 2
[20:48:53] <consfearacy> so i had two different pips
[20:49:13] <consfearacy> to fix that i had to remove python3
[20:49:19] <consfearacy> but it still remains somehow
[20:50:49] <consfearacy> so which pip should i use?
[20:55:38] <mgedmin> it's not a problem to have multiple pythons or multiple pips
[20:55:56] <consfearacy> ok then great
[20:56:19] <mgedmin> when in doubt you can select the one you want with python2 -m pip or python3 -m pip
[20:56:29] <mgedmin> (assuming there's a python2; sometimes it's just python for python 2.x)
[20:56:53] <mgedmin> and by "select the one you want" I meant things like python3 -m pip install some-library-you-want-to-use-with-python3
[20:57:17] <consfearacy> ah ok thanks thats a good trick
[20:57:53] <nanonyme> Or py -2 -m pip and py -3 -m pip if you happen to be miserable enough to use Windows
[21:03:17] <mgedmin> slackware was mentioned so