Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment:
There are two kinds of configuration files supported in Packaging, and you can
say it maybe a transition consideration from distutils/setuptools to
Packaging, but if you look into the documents of Packaging(you can generate it
from the /Doc directory), you will get to know that Packaging has a more
further and important consideration - setup.cfg and setup.py place different
roles in a project, setup.py offers developers to set while setup.cfg offers
users to edit in a cheap and easy way... Certainly you can set anyone of these
two files to reach the same goal.
>
>I think I understand that much. The point of setup.cfg is to do away with the
>completely ad-hoc nature of code that developers can put into setup.py, which
>prevents playing nicely with distro package managers. I'm fairly sure I've
>seen Tarek say that "for developers, no more setup.py" - in fact, I've just
>found where he said it:
http://tarekziade.wordpress.com/2011/05/22/packaging-has-landed-in-the-stdlib/
and also
http://pycon.tv/#/video/57 (at around 6:55 into the video, and at 8:30 - "there
is no more setup.py" - meaning in the new way of doing things)
So the role of setup.py is historical, and the way developers customise
installations is through using hooks. These work well enough, and I am
currently using them in the nemo project which is a companion to the pythonv
branch - see http://www.red-dove.com/screencasts/pythonv/pythonv.html
----------
Added file: http://bugs.python.org/file22933/unnamed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12394>
_______________________________________
<html><body><div style="color:#000; background-color:#fff; font-family:tahoma,
new york, times, serif;font-size:10pt"><div id="yiv159912332"><div
style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family:
tahoma,new york,times,serif; font-size: 10pt;"><div
id="yiv159912332yui_3_2_0_14_131367940402095"><br><blockquote
id="yiv159912332yui_3_2_0_14_131367940402054" style="border-left: 2px solid
rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div
id="yiv159912332yui_3_2_0_14_131367940402094"
class="yiv159912332yui_3_2_0_14_131367940402057" style="font-family: tahoma,new
york,times,serif; font-size: 10pt;"><div
id="yiv159912332yui_3_2_0_14_131367940402093"
class="yiv159912332yui_3_2_0_14_131367940402059" style="font-family: times new
roman,new york,times,serif; font-size: 12pt;">There are two kinds of
configuration files supported in Packaging, and you can say it maybe a
transition consideration from distutils/setuptools to
Packaging, but if you look into the documents of Packaging(you can generate it
from the /Doc directory), you will get to know that Packaging has a more
further and important consideration - setup.cfg and setup.py place
different roles in a project, setup.py offers developers to set while
setup.cfg offers users to edit in a cheap and easy way... Certainly you can set
anyone of these two files to reach the same
goal.<br><span></span></div></div></blockquote>I think I understand that much.
The point of setup.cfg is to do away with the completely ad-hoc nature of code
that developers can put into setup.py, which prevents playing nicely with
distro package managers. I'm fairly sure I've seen Tarek say that "for
developers, no more setup.py" - in fact, I've just found where he said
it:</div><div id="yiv159912332yui_3_2_0_14_131367940402095"><br></div><div
id="yiv159912332yui_3_2_0_14_131367940402095">http://tarekziade.wordpress.com/2011/05/22/packaging-has-landed-in-the-stdlib/</div><div
id="yiv159912332yui_3_2_0_14_131367940402095"><br></div><div
id="yiv159912332yui_3_2_0_14_131367940402095">and also<br></div><div
id="yiv159912332yui_3_2_0_14_131367940402095"><br></div><div
id="yiv159912332yui_3_2_0_14_131367940402095">http://pycon.tv/#/video/57 (at
around 6:55
into the video, and at 8:30 - "there is no more setup.py" - meaning in the new
way of doing things)<br></div><div
id="yiv159912332yui_3_2_0_14_131367940402095"><br></div><div
id="yiv159912332yui_3_2_0_14_131367940402095">So the role of setup.py is
historical, and the way developers customise installations is through using
hooks. These work well enough, and I am currently using them in the nemo
project which is a companion to the pythonv branch - see
http://www.red-dove.com/screencasts/pythonv/pythonv.html</div><div
id="yiv159912332yui_3_2_0_14_131367940402095"><br></div><div
id="yiv159912332yui_3_2_0_14_131367940402095"><br><div
id="yiv159912332yui_3_2_0_14_131367940402094"
class="yiv159912332yui_3_2_0_14_131367940402057" style="font-family: tahoma,new
york,times,serif; font-size: 10pt;"><div
id="yiv159912332yui_3_2_0_14_131367940402093"
class="yiv159912332yui_3_2_0_14_131367940402059" style="font-family: times new
roman,new york,times,serif; font-size:
12pt;"><br></div></div></div></div></div></div></body></html>
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
