Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#4671 closed enhancement (fixed)


Reported by: Fernando de Oliveira Owned by: Fernando de Oliveira
Priority: normal Milestone:
Component: BOOK Version: SVN
Severity: normal Keywords:


Change History (7)

comment:1 by Fernando de Oliveira, 9 years ago

Owner: changed from blfs-book@… to Fernando de Oliveira
Status: newassigned

comment:2 by Fernando de Oliveira, 9 years ago

I would like to have a suggestion about the docs, because of conflict with Python2 docs. What I am looking for is to change either 2 and/or 3 docs place/env var, something could be done, I think.

Any suggestions, would be much appreciated, thanks.

comment:3 by Armin K, 9 years ago

Since they seem to be developer docs, and Python guys recommend writing new software against Python 3 since Python 2 is in maintenance mode, I suggest keeping Python 3 ones and removing Python 2 ones entirely.

comment:4 by Fernando de Oliveira, 9 years ago

Thanks, very much.

I will do almost that: I will slightly modify what you have written in comment 3 and add to Python 2:

"Since Python 2 is in maintenance mode, and it is recommended by upstream that Python 3 be used for development, you will probably not need to install the documentation, if the newer Python is or will be installed in the system. However, if you still want to install both documentations, be sure to define PYTHONDOCS variable to the version you want to use, each time you need to consult the documentation."

I was thinking if I could, instead, use an sed to modify PYTHONDOCS: sed /PYTHONDOCS/PYTHON2DOCS/g' in all directory, before building. But am not sure if that would work.

comment:5 by bdubbs@…, 9 years ago

That seems to be a reasonable approach. I can see the potential for a developer needing the older docs, but then developers should be able to figure it out on their own.

comment:6 by Fernando de Oliveira, 9 years ago

Resolution: fixed
Status: assignedclosed

Thanks, for both of you. That is done.

Fixed at r12689.

comment:7 by bdubbs@…, 9 years ago

Milestone: current

Milestone current deleted

Note: See TracTickets for help on using tickets.