1:39 p.m.
Hello together,
can someone point me to the part of the Python packaging guidelines,
which explicitly says .egg-info *MUST* be removed before build?
Cheers,
Björn
2:05 p.m.
On Sáb, 2016-10-22 at 20:39 +0200, Björn
Hello together,
can someone point me to the part of the Python packaging guidelines,
which explicitly says .egg-info *MUST* be removed before build?
https://fedoraproject.org/wiki/Packaging:Python_Eggs#Upstream_Egg_Packages
Cheers,
Björn
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
--
Sérgio M. B.
3:26 p.m.
Am Samstag, den 22.10.2016, 20:05 +0100 schrieb Sérgio Basto:
On Sáb, 2016-10-22 at 20:39 +0200, Björn
> Hello together,
>
> can someone point me to the part of the Python packaging
> guidelines,
> which explicitly says .egg-info *MUST* be removed before build?
https://fedoraproject.org/wiki/Packaging:Python_Eggs#Upstream_Egg_Pac
kages
Well, I'm sorry, but this does not answer my question… The cited
guideline says:
Do not distribute egg packages from upstream.
I agree with that, but that is not the case for a tarball from PyPi
containing a '%{pypi_name}.egg-info'-folder. This is about pre-built,
specificly to the a certain Python-version (and in most cases operating
system and binary-arch), '%{pypi_name}-%{version}.egg'-files
distributed on PyPi…
In Fedora, all packages must be rebuilt from source. An egg package
(which is different from egg metadata) contains compiled bytecode and
may, if it contains a C extension, contain compiled binary extensions
as well.
Here the guideline distinguishes between a pre-built *.egg-file and
egg-metadata (*.egg-info-folder).
I cannot find anything saying it is required to remove the egg-metadata
(.egg-info) before building the sources; it isn't even mentioned in the
common sample spec-file [1]…
[1] https://fedoraproject.org/w/index.php?title=Packaging:Python#Examp
le_common_spec_file
9:47 a.m.
On 10/22/2016 04:26 PM, Björn "besser82" Esser wrote:
Am Samstag, den 22.10.2016, 20:05 +0100 schrieb Sérgio Basto:
> On Sáb, 2016-10-22 at 20:39 +0200, Björn
>> Hello together,
>>
>> can someone point me to the part of the Python packaging
>> guidelines,
>> which explicitly says .egg-info *MUST* be removed before build?
>
>
> https://fedoraproject.org/wiki/Packaging:Python_Eggs#Upstream_Egg_Pac
> kages
Well, I'm sorry, but this does not answer my question… The cited
guideline says:
> Do not distribute egg packages from upstream.
I agree with that, but that is not the case for a tarball from PyPi
containing a '%{pypi_name}.egg-info'-folder. This is about pre-built,
specificly to the a certain Python-version (and in most cases operating
system and binary-arch), '%{pypi_name}-%{version}.egg'-files
distributed on PyPi…
> In Fedora, all packages must be rebuilt from source. An egg package
> (which is different from egg metadata) contains compiled bytecode and
> may, if it contains a C extension, contain compiled binary extensions
> as well.
Here the guideline distinguishes between a pre-built *.egg-file and
egg-metadata (*.egg-info-folder).
I cannot find anything saying it is required to remove the egg-metadata
(.egg-info) before building the sources; it isn't even mentioned in the
common sample spec-file [1]…
I don't think it's explicitly mandated, but it's always recommended,
particularly if you need to patch setup.py at all (for example, I have a package
that I need to tweak the dependency versions for because upstream uses == all
the time when they don't strictly need to). Deleting the pre-existing .egg-info
file ensures that it gets regenerated including any changes you may have made.
2792
days inactive
2794
days old
3 comments
3 participants
participants (3)
-
Björn "besser82" Esser -
Stephen Gallagher -
Sérgio Basto