<div dir="ltr"><div class="gmail_quote"><div dir="ltr">Zbigniew Jędrzejewski-Szmek <<a href="mailto:zbyszek@in.waw.pl">zbyszek@in.waw.pl</a>> schrieb am Fr., 31. Juli 2015 um 06:06 Uhr:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Jul 30, 2015 at 07:34:48PM -0500, Jason L Tibbitts III wrote:<br>
> After some additional discussion and cleanup, I've gone ahead and moved<br>
> my drafts into place in the main guidelines. Please let me know if I've<br>
> made any mistakes or typos or left out anything important.<br>
There's a dead link in "Example common spec file".<br>
<br>
> However, there is one thing I'm trying to understand about the new<br>
> guidelines (which came from one of the submitted drafts, not something<br>
> that I wrote). They say:<br>
><br>
> "<br>
> The following is a very simple spec file for a module building for both<br>
> python2 and python3. It builds both versions in the same directory; this<br>
> is possible because setuptools uses different build directories for<br>
> different python versions and architectures. In addition, python3 will<br>
> include the version of the interpreter in the names of generated files,<br>
> so the build products don't conflict. (Of course this only works if a<br>
> package builds for a single python2 version, which should always be the<br>
> case in Fedora.)<br>
> "<br>
><br>
> Which is fine, except that I must be missing something about the second<br>
> sentence. Setuptools in f22 and rawhide (which I know are different<br>
> versions) seems to use "build" regardless of which python version is<br>
> used to execute setup.py. Am I misunderstanding what that sentence is<br>
> trying to tell me?<br>
I wrote that. I turns out, which I didn't know at the time, that this is<br>
only true for binary modules<br>
(for example python-systemd has build/{lib,temp}.linux-x86_64-{2.7,3.4}).<br>
For pure-python modules it seems to use a single build directory,<br>
but separate build/scripts directories.<br>
<br>
[ It seems that there's no nice way to tell setuptools/distutils/distribute<br>
to always use separate build directories. It still uses the same build<br>
directory even if 2to3 translation is specified in the setup.py file, which is<br>
probably a bug. In a pinch, it is possible to override the build dir with<br>
--build-lib. So something like this works, even if 2to3 is used:<br>
%{__python2} setup.py build --build-lib build/2<br>
%{__python3} setup.py build --build-lib build/3<br>
Fortunately this is rarely necessary.]<br></blockquote><div><br></div><div>So either this is a bug in the case of 2to3 or the %py{2,3}_build macros should implement this to work around it? Otherwise these packages would need to be build within different build directories and the current pushd/popd boilerplate.</div><div><br></div><div> -Tom</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So I think the detailed justification should be removed, and the first<br>
paragraph of "Example common spec file" replaced with something like this:<br>
<br>
"The following is a very simple spec file for a module building for<br>
both python2 and python3. It builds both versions in the same<br>
directory; this is possible because build products for different<br>
versions of Python usually do not conflict."<br>
<br>
> For the package I'm using for testing (python-requests) it turns out<br>
> that the results of %py2_build and %py3_build are completely identical,<br>
> but this might just be coincidence.<br>
<br>
Zbyszek<br>
_______________________________________________<br>
python-devel mailing list<br>
<a href="mailto:python-devel@lists.fedoraproject.org" target="_blank">python-devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/python-devel" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/python-devel</a></blockquote></div></div>