sborg63
2018-08-26 16:00:37 UTC
Hi all,
There are python programs that no longer depend on setup.py scripts
using install but exclusively on those that use pip (for example LEO, as
described below). How are we dealing with this? Is there a way of
adapting the Slackbuilds for such programs or do we accept that pip
becomes another way of dealing with python (It already is part of the
python distribution in current)? Or do we ask upstream to keep providing
a setup.py that can use install?
Background:
As a response to my request for a setup.py install script for the
LEO editor (https://github.com/leo-editor/leo-editor/issues/810), the
answer is to use pip: The recent version has changed to a complete
pip-install and bypasses the possibility of using the setup.py install
method. The latter is -as far as I have been using python
modules/packages in Slackware- the method of choice to build a package
via a SlackBuild which produces a tgz-package that can then be
installed/updated using the common slackware tools.
The idea behind the pip-only install is that determining
updates/dependencies is much easier (with the presumed improvements
linked below). At the moment on SBo these dependencies have been sorted
out (and SlackBuilds made available) which allows a slacker to use one
install-method (the distribution-specific tools) instead of a mixture
of tools (distribitution plus tool-specific methods (like pip for
python)).
Cheers,
Rob
Begin forwarded message:
Date: Sun, 26 Aug 2018 01:05:16 -0700
From: matt wilkie <***@github.com>
To: leo-editor/leo-editor <leo-***@noreply.github.com>
Cc: brobr <***@disroot.org>, Author <***@noreply.github.com>
Subject: Re: [leo-editor/leo-editor] "python setup.py install" does not
complete (#810)
https://github.com/leo-editor/leo-editor/tree/5.6/leo/dist and will be
there for as long as Github is. Copying from the Github tag to root of
a local Leo folder is functionally equivalent to copying from local
dist folder to root:
wget
https://raw.githubusercontent.com/leo-editor/leo-editor/5.6/leo/dist/setup.py
\ -O=~/my-leo-distrib/setup.py
related to pip. Sooner or later using the old version will probably
stop working. [Pip solves a lot of
problems](https://stackoverflow.com/a/15731459/14420), are you sure you
can't use it? If there are specific reasons you can't, re-open this
issue and we can explore what might be done. I'll need information and
feedback though as I don't know about building distribution packages.
There are python programs that no longer depend on setup.py scripts
using install but exclusively on those that use pip (for example LEO, as
described below). How are we dealing with this? Is there a way of
adapting the Slackbuilds for such programs or do we accept that pip
becomes another way of dealing with python (It already is part of the
python distribution in current)? Or do we ask upstream to keep providing
a setup.py that can use install?
Background:
As a response to my request for a setup.py install script for the
LEO editor (https://github.com/leo-editor/leo-editor/issues/810), the
answer is to use pip: The recent version has changed to a complete
pip-install and bypasses the possibility of using the setup.py install
method. The latter is -as far as I have been using python
modules/packages in Slackware- the method of choice to build a package
via a SlackBuild which produces a tgz-package that can then be
installed/updated using the common slackware tools.
The idea behind the pip-only install is that determining
updates/dependencies is much easier (with the presumed improvements
linked below). At the moment on SBo these dependencies have been sorted
out (and SlackBuilds made available) which allows a slacker to use one
install-method (the distribution-specific tools) instead of a mixture
of tools (distribitution plus tool-specific methods (like pip for
python)).
Cheers,
Rob
Begin forwarded message:
Date: Sun, 26 Aug 2018 01:05:16 -0700
From: matt wilkie <***@github.com>
To: leo-editor/leo-editor <leo-***@noreply.github.com>
Cc: brobr <***@disroot.org>, Author <***@noreply.github.com>
Subject: Re: [leo-editor/leo-editor] "python setup.py install" does not
complete (#810)
Could such a setup.py be restored in the 'leo/dist/' folder of 5.7
[...}
The 5.6 setup.py and friends can be found at[...}
https://github.com/leo-editor/leo-editor/tree/5.6/leo/dist and will be
there for as long as Github is. Copying from the Github tag to root of
a local Leo folder is functionally equivalent to copying from local
dist folder to root:
wget
https://raw.githubusercontent.com/leo-editor/leo-editor/5.6/leo/dist/setup.py
\ -O=~/my-leo-distrib/setup.py
...for those who like to create distribution-specific packages (and
want to bypass pip)?
There have a been changes in setup.py since 5.6 not specificallywant to bypass pip)?
related to pip. Sooner or later using the old version will probably
stop working. [Pip solves a lot of
problems](https://stackoverflow.com/a/15731459/14420), are you sure you
can't use it? If there are specific reasons you can't, re-open this
issue and we can explore what might be done. I'll need information and
feedback though as I don't know about building distribution packages.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/leo-editor/leo-editor/issues/810#issuecomment-416021532
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/leo-editor/leo-editor/issues/810#issuecomment-416021532