PMXBOT Log file Viewer

Help | Karma | Search:

#pypa logs for Tuesday the 17th of June, 2014

(Back to #pypa overview) (Back to channel listing) (Animate logs)
[11:51:24] <zesus_> Hello! We uploaded our first wheel of robotframework with "setup.py bdist_wheel upload". The uploaded wheel got python version 2.7, although it really is version independent. Does this matter? Should we do something for it to get version "any"?
[11:51:42] <zesus_> or does it make any difference?
[11:52:08] <ionelmc> zesus_: in setup.cfg add:
[11:52:11] <ionelmc> https://www.irccloud.com/pastebin/nxrp5TsQ
[11:55:04] <zesus_> ionelmc: alright, thanks!
[11:55:26] <zesus_> I guess I cant edit the wheel already uploaded? I need to remove the old one and do the upload again?
[11:55:37] <zesus_> to change that target.
[12:00:25] <zesus_> ionelmc: hum, that actually creates a file called robotframework-2.8.5-py2.py3-none-any.whl but leaves the py version to 2.7 at the downloads list.
[12:03:26] <zesus_> sorry for the ambiguity, I meant the py version column I see at pypi downloads.
[12:19:57] <ionelmc> zesus_: packaging mistakes usually require manual correction :)
[12:20:19] <ionelmc> remove it from the pypi ui
[14:11:58] <dstufft> zesus_: that field doesn't matter
[15:32:13] <nlloret_dba> Hi
[15:32:53] <nlloret_dba> Is there a way to use pip with --upgrade option, but in a idempotent way?
[15:33:01] <nlloret_dba> I explain myself bit more:
[15:33:25] <nlloret_dba> pip install foo --upgrade
[15:33:45] <nlloret_dba> it will always remove foo and reinstall it, even if the same version of the library is already installed
[15:34:17] <nlloret_dba> is any way to avoid this? I mean, any way to get "pip install foo --upgrade" to only reinstall the library when there is a version higher to be installed?
[15:34:23] <tomprince> Is there a way to get setuptools to install a console_script somewhere other than bin/ ?
[15:42:34] <nlloret_dba> Is there a way to use "pip install foo --upgrade" and only have foo re-installed when there is a newer version available (actually, pip ... --upgrade always does an uninstall + install)
[16:56:39] <nlloret_dba> Is there a way to use "pip install foo --upgrade" and only have foo re-installed when there is a newer version available (actually, pip ... --upgrade always does an uninstall + install)
[16:59:32] <dstufft> nlloret_dba: it should do that by default
[16:59:50] <nlloret_dba> mmm...
[17:00:10] <nlloret_dba> pip / python 2.7 ?
[17:00:24] <nlloret_dba> (that is what i am using now, I haven't checked with newer versions)
[17:03:59] <dstufft> what version of pip
[17:19:29] <nlloret_dba> holy ***
[17:19:33] <nlloret_dba> thanx dstufft
[17:19:44] <dstufft> nlloret_dba: ?
[17:19:45] <nlloret_dba> on the remote server pip was on version 1.0....
[17:19:48] <dstufft> ah
[17:19:52] <dstufft> yea that doesn't surprise me
[17:19:57] <dstufft> you're probably using ubuntu 12.04?
[17:20:02] <nlloret_dba> yes
[17:20:08] <dstufft> yea, that's the version that came in ubuntu
[17:20:10] <nlloret_dba> that seems to be the default
[17:20:21] <nlloret_dba> yeps
[17:20:49] <nlloret_dba> upgrading to newer version did the job
[17:21:11] <nlloret_dba> thanx, and sorry.. quite a newbie question :P
[17:21:22] <dstufft> np :)
[19:31:18] <jax> hm
[19:31:31] <jax> what did i mess up, if running 'supervisorctl' gives the output of running 'pip' ? :D
[19:41:43] <dstufft> wat
[19:41:46] <dstufft> I have no idea
[20:30:33] <zesus_> dstufft: thanks! thats what we figured. We will leave the py version to 2.7 for now.