aving to build your own
Python feels like an unnecessary hurdle (IMHO).
FWIW as a Python extension author and maintainer I have taken advantage
of these deubg builds, it's very useful.
If you're developing at the level of CPython you probably also have the
skill to build yo
I made this comment previously but because I think it's important I'm
going to repeat it.
Fedora's Python version migration needs to be coordinated with RHEL.
Yes I know Fedora is independent of both Red Hat and RHEL but the real
world reality is spec files are shared between both. At the mome
On 02/02/2017 11:19 PM, Sérgio Basto wrote:
Hello ,
I'd like use this gdb python [1] , but can't put it work on Fedora 24,
last problems mentioned are about Fedora 13 , can someone help me on
pointing how I could use New_gdb_commands [2] ?
Contact David Malcolm , he is the author.
Thanks ,
[
On 05/27/2016 10:10 AM, Tomas Orsava wrote:
I think the python2-XXX package in the examples is missing something
like this:
Requires: %{_bindir}/sample-exec
Make sense?
I believe there is a misunderstanding. In your first message you said
"But the guidelines require the py3 version of the scr
On 05/26/2016 08:24 AM, Tomas Orsava wrote:
Hi,
those are very good questions to which you should be able to find
answers on the Python RPM Porting Guide [0]. You are right that this
should be better covered in the packaging guidelines, sadly the process
of changing them is rather problematic so
With reference to the guidelines for Python packaging found here:
https://fedoraproject.org/wiki/Packaging:Python
Specifically the material concerning executables in /usr/bin.
In the "Example common spec file" section is this comment.
# Must do the python2 install first because the scripts in
On 05/13/2016 03:43 PM, Jason L Tibbitts III wrote:
FYI, an updated python macros package is in Rawhide which includes
the sleep.
Thank you.
I don't think manually deleting some random at a special place in
the spec is a proper solution.
+1
setuptools should really be either fixed upstrea
On 05/12/2016 11:24 AM, Tomas Orsava wrote:
On 05/12/2016 05:16 PM, Miro Hrončok wrote:
On 12.5.2016 15:24, John Dennis wrote:
On 05/11/2016 11:54 AM, Petr Viktorin wrote:
On 05/11/2016 05:16 PM, John Dennis wrote:
The workaround I came up with is to delay the execution of
%py3_build by
at
On 05/11/2016 11:54 AM, Petr Viktorin wrote:
On 05/11/2016 05:16 PM, John Dennis wrote:
The workaround I came up with is to delay the execution of %py3_build by
at least 1 second by inserting a sleep in-between the %py2_build and
%py3_build macros in the spec file, like this:
%py2_build
sleep
I've been following the guidelines for Python packaging found here:
https://fedoraproject.org/wiki/Packaging:Python
in particular the cookbook for supporting both Py2 and Py3.
I've discovered two places where things fail to work as expected with
respect to script installation. Both of these pr
10 matches
Mail list logo
