Message85204
It strikes me as an inconsistency because I wouldn't expect the build
process to differ from Python 3.0 to 3.1 except for fixing bugs. A
developer, or someone trying to keep up with the most recent
versions, who had been successfiully making the html doc in a
subversion copy of Python 3.0 and wanted to move over to Python 3.1
finds this surprise if the command python is bound to Python 3. I
grant you that this is a lot of ifs, and a transitional issue if
we're all going to call Python 3 python3.
It might even be worth mentioning in the build instructions that
"python" should be bound to a Python 2 executable, not Python 3,
because a few things, such as make html in doc, use tools that
haven't been updated.
Not a big deal. Just fighting for the "Principle of Least Surprise",
as in many of the documentation issues I've submitted. My GUI
background showing.
--
--
--- Mitchell |
File name |
Uploaded |
unnamed
|
MLModel,
2009-04-02.14:36:47
|
|
Date |
User |
Action |
Args |
2009-04-02 14:36:50 | MLModel | set | recipients:
+ MLModel, georg.brandl |
2009-04-02 14:36:49 | MLModel | link | issue5658 messages |
2009-04-02 14:36:49 | MLModel | create | |
|