Opened 9 years ago
Closed 9 years ago
#6288 closed enhancement (fixed)
Setuptools-14.3.1
Reported by: | Pierre Labastie | Owned by: | Fernando de Oliveira |
---|---|---|---|
Priority: | normal | Milestone: | 7.8 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
New point version https://pypi.python.org/packages/source/s/setuptools/setuptools-14.3.1.tar.gz MD5: cdba2741b16acaa3ed06c2252623f6b9
CHANGES 14.3.1 -Issue #307: Removed PEP-440 warning during parsing of versions in pkg_resources.Distribution. -Issue #364: Replace deprecated usage with recommended usage of EntryPoint.load.
Change History (4)
comment:1 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
follow-up: 3 comment:2 by , 9 years ago
Thanks for the update, Fernando.
Well, I discovered python packaging when I first added setuptools, so there is a high probability I have not done things right. Let me just give some reasonning I have had: for me, all .jar ands .egg are libraries, because the real programs are java and python respectively: specially for python packages, you include them with "import <module>".
However, my main concern is "in which rubric to put them if not in libraries?". Certainly not in "Installed programs" or "Installed directories". Maybe we could add another rubric for those (I do not have a proposition for the rubric name at the moment).
About the difference between the DESTDIR and the direct install, I have mentionned it in a mail: http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-March/029838.html Moving the egg-info directory and the other files to their final places gives a functional package, although it is different from what you obtain from a direct install.
comment:3 by , 9 years ago
Replying to pierre.labastie:
Well, I discovered python packaging when I first added setuptools, so there is a high probability I have not done things right.
On the contrary. I found it very interesting how you simplified. If I had done it, I would copy (duplicate) the sources, increasing the size and the numbers of cd or pushd popd, much more complicated.
Let me just give some reasonning I have had: for me, all .jar ands .egg are libraries, because the real programs are java and python respectively: specially for python packages, you include them with "import <module>".
I disagree with the argument, so a "Basic" "program" or any other program is a library, if the language is interpreted?
However, my main concern is "in which rubric to put them if not in libraries?". Certainly not in "Installed programs" or "Installed directories". Maybe we could add another rubric for those (I do not have a proposition for the rubric name at the moment).
I had the same thought. And after all, they are under the .../lib/ hierarchy.
About the difference between the DESTDIR and the direct install, I have mentionned it in a mail: http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-March/029838.html Moving the egg-info directory and the other files to their final places gives a functional package, although it is different from what you obtain from a direct install.
I had forgotten your post. Very good post, thanks.
OK, will keep it as you did.
Thanks for the reply.
Pierre, I am trying to update this package, but have twp problems:
First, DESTDIR (--root=) installs setuptools-14.3.1-pyx.y.egg-info, not setuptools-14.3.1-pyx.y.egg.
Second, a .egg can contain the complete package, including code, resources, and metadata. Thus, I'm having difficulty understanding it to be listed under libraries. If there is any .jar in the book listed, how can one differentiate a program from a library? ISTR a program that uas .jar.
Of course, I don't like to discuss, so, the intention is really to learn. This doubt has kept me searching and reading most part of this day, so I will have to rest, because I'm amost blind, no matter how much I use CTRL++.