[issue5309] setup.py doesn't parallelize extension module compilation

Changes by Mark Lawrence : -- components: +Distutils2 -Distutils nosy: +eric.araujo versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker ___ __

[issue5309] setup.py doesn't parallelize extension module compilation

Éric Araujo added the comment: Do you want to work on a patch? -- stage: -> needs patch versions: +Python 2.5, Python 2.6, Python 2.7, Python 3.1 ___ Python tracker ___

[issue5309] setup.py doesn't parallelize extension module compilation

Changes by Éric Araujo : -- versions: +3rd party -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___

[issue5309] setup.py doesn't parallelize extension module compilation

Changes by Éric Araujo : -- keywords: +gsoc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue5309] setup.py doesn't parallelize extension module compilation

Antoine Pitrou added the comment: The original request is really about setup.py, not packaging. I don't care about packaging, and it's not in the stdlib. -- assignee: tarek -> components: +Build -Distutils2 title: packaging doesn't parallelize extension module compilation -> setup.py

[issue5309] setup.py doesn't parallelize extension module compilation

Christian Heimes added the comment: +1 I think it's sufficient to parallelize the compilation step (.c -> .o) and ignore the linker step. Linking is usually so fast that it doesn't matter. Idea: * separate compile step from link step * run all compile calls for all extensions in parallel until

[issue5309] setup.py doesn't parallelize extension module compilation

New submission from Antoine Pitrou : When run with "make -jN", the Python compilation process is able to parallelize across N concurrent processes for the interpreter core, but extension modules are still compiled sequentially. -- assignee: tarek components: Distutils messages: 82447 nos