That's cool, but historical heritage makes the make argument
somewhat confusing for new users. The immediate question I
can sense is What is the difference between build and make?
To make (this word again) the critics constructive, let me pass
some ideas about ideal user experience as I see it.
[If you want to continue this discussio, please move it from python-dev to
sphinx-users. It is now completely offtopic for the former.]
Anyway, just as a short explanation, you missed the point of the change:
-M is not meant to be used directly but still via a (very short)
Makefile. This isn't
What about using venv and pip instead of svn?
On Sun, Jan 12, 2014 at 4:12 PM, Georg Brandl g.bra...@gmx.net wrote:
Am 11.01.2014 21:11, schrieb Terry Reedy:
On 1/11/2014 2:04 PM, georg.brandl wrote:
http://hg.python.org/cpython/rev/87bdee4d633a
changeset: 88413:87bdee4d633a
branch:
Planned :)
Georg
Am 12.01.2014 09:12, schrieb INADA Naoki:
What about using venv and pip instead of svn?
On Sun, Jan 12, 2014 at 4:12 PM, Georg Brandl g.bra...@gmx.net
mailto:g.bra...@gmx.net wrote:
Am 11.01.2014 21:11, schrieb Terry Reedy:
On 1/11/2014 2:04 PM, georg.brandl
And cross-platform automation tools in Python instead of make
https://bitbucket.org/birkenfeld/sphinx/issue/456/makepy-command-script
--
anatoly t.
On Sun, Jan 12, 2014 at 11:12 AM, INADA Naoki songofaca...@gmail.com wrote:
What about using venv and pip instead of svn?
On Sun, Jan 12, 2014
