[Python-Dev] How best to handle the docs for a renamed module? (original) (raw)
André Malo nd at perlig.de
Fri May 16 14:52:19 CEST 2008
- Previous message: [Python-Dev] How best to handle the docs for a renamed module?
- Next message: [Python-Dev] How best to handle the docs for a renamed module?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- M.-A. Lemburg wrote:
On 2008-05-12 04:34, Brett Cannon wrote: > For the sake of argument, let's consider the Queue module. It is now > named queue. For 2.6 I plan on having both Queue and queue listed in > the index, with Queue deprecated with instructions to use the new > name. > > But what to do about all the references. Should we leave them pointing > at Queue to lessen confusion for people who read about some module on > some other site that isn't using the new name, or update everything in > 2.6 to use the new name?
How hard would it be to add a redirects from the old pages to the new ones ? modrewrite does wonders - well, provided you find the right patterns...
The "pattern" can be a simple text file maintained in subversion::
oldurl newurl ...
And then you can utilize RewriteMap to get that into the apache.
nd
- Previous message: [Python-Dev] How best to handle the docs for a renamed module?
- Next message: [Python-Dev] How best to handle the docs for a renamed module?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]