Menu
▾
▴
docutils-develop
|
From: Beni C. <cb...@us...> - 2004-09-15 13:35:42
|
Some time ago, pep2html.py was deleted from the docutils CVS. Apparently, it was decided that since it's barely a proper docutils frontend and mostly a parser for the old PEP format and a repository of PEP maintainance it belongs in the Python CVS. OK with me. Now the problem is that the copy of docutils that comes with pep2html.py in the Python CVS (under `nondist/peps/`__) is a very old version, which lack some essential features like understanding the new config sections, so my /etc/docutils.conf and ~/.docutils don't work with it. I fixed it by replacing the nondist/peps/docutils directory by a symlink to the up-to-date docutils on my machine. The proper fix is probably updating the docutils in Python CVS. __ http://cvs.sf.net/viewcvs.py/python/python/nondist/peps/ -- Beni Cherniavsky <cb...@us...> Note: I can only read email on week-ends... |
|
From: Felix W. <Fel...@gm...> - 2004-09-15 18:38:27
|
Beni Cherniavsky wrote: > Some time ago, pep2html.py was deleted from the docutils CVS. I'm not sure right now why we deleted it. There is quite a lot of code in pep2html.py, and pep.py is much shorter. David, any idea? We didn't delete pep2html.py while it should have been pep.py, did we? > Apparently, it was decided that since it's barely a proper docutils > frontend and mostly a parser for the old PEP format and a repository > of PEP maintainance it belongs in the Python CVS. OK with me. > > Now the problem is that the copy of docutils that comes with > pep2html.py in the Python CVS (under `nondist/peps/`__) is a very > old version I don't see much point in having a copy of Docutils in the Python CVS. Why not just add a note that Docutils is required to process the pep files? -- When replying to my email address, please ensure that the mail header contains 'Felix Wiemann'. http://www.ososo.de/ |
|
From: Fred L. D. Jr. <fd...@ac...> - 2004-09-15 19:32:35
|
On Wednesday 15 September 2004 02:38 pm, Felix Wiemann wrote: > I don't see much point in having a copy of Docutils in the Python CVS. > Why not just add a note that Docutils is required to process the pep > files? As I recall, docutils was moving more quickly at the time, and wasn't being released regularly, so there was some merit in freezing which version was used for PEPs. Another factor was to avoid the additional checkout which would have been needed. I'd be happy enough to see this changed, but I suspect there are still others who will disagree. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> |
|
From: David G. <go...@py...> - 2004-09-16 02:41:08
Attachments:
signature.asc
|
[Beni Cherniavsky]
>> Some time ago, pep2html.py was deleted from the docutils CVS.
It was 2004-07-27.
[Felix Wiemann]
> I'm not sure right now why we deleted it.
From the 2004-07-27 Docutils Bug Day IRC transcript (edited slightly):
felixw: Who needs pep2html.py? (Except you?) It looks like most users
will want to use pep.py, but maybe I'm wrong.
davidg: we could get rid of pep2html.py from Docutils, since it's a
duplicate of what's in Python's CVS. but I wouldn't rename
pep.py to pep2html.py: too confusing
davidg: PEP authors use it, but probably Python's copy
felixw: pep.py shouldn't be installed by default, should it? It seems
too specific.
davidg: probably not. [...]
felixw: Does Python have a copy of pep.py, too?
davidg: no, doesn't need it. pep2html.py is enough
BTW, we should do another Bug Day soon, especially if others could
join in. It would be more fun if it weren't just Felix & me.
> There is quite a lot of code in pep2html.py, and pep.py is much
> shorter.
tools/pep.py only processes reST PEPs, not plaintext PEPs.
pep2html.py does both, and has more features (installing PEPs on
www.python.org, etc.).
> David, any idea? We didn't delete pep2html.py while it should have
> been pep.py, did we?
No.
>> Apparently, it was decided that since it's barely a proper docutils
>> frontend and mostly a parser for the old PEP format and a repository
>> of PEP maintainance it belongs in the Python CVS. OK with me.
Nothing to do with being a proper Docutils front end or not. Just a
maintenance issue. If you're dealing with Python PEPs, you'll have
Python's nondist/peps/ from CVS, so you'll have pep2html.py. There
are probably more PEP authors who happen to use Docutils than Docutils
users who happen to write PEPs.
>> Now the problem is that the copy of docutils that comes with
>> pep2html.py in the Python CVS (under `nondist/peps/`__) is a very
>> old version, which lack some essential features like understanding
>> the new config sections, so my /etc/docutils.conf and ~/.docutils
>> don't work with it. I fixed it by replacing the
>> nondist/peps/docutils directory by a symlink to the up-to-date
>> docutils on my machine.
That's a valid fix.
>> The proper fix is probably updating the docutils in Python CVS.
Yes, I agree. An update of Docutils in Python CVS
(nondist/peps/docutils) is overdue. I will do it soon.
> I don't see much point in having a copy of Docutils in the Python
> CVS. Why not just add a note that Docutils is required to process
> the pep files?
Fred's recollection sounds right. The Python developers asked if
Docutils could be included to make PEP editing & processing easier.
There's no harm in having a copy of Docutils there, so I agreed. And
it's not much effort to update it (I think I wrote a script to help).
I just haven't done it recently, but I will soon.
--
David Goodger <http://python.net/~goodger>
|
|
From: Felix W. <Fel...@gm...> - 2004-09-16 18:18:19
|
David Goodger wrote: > Felix Wiemann wrote wrote: > >> I'm not sure right now why we deleted [pep2html.py]. > > From the 2004-07-27 Docutils Bug Day IRC transcript (edited slightly): I forgot to save a transcript myself. Would you send me a copy (or post/publish the transcript)? > davidg: we could get rid of pep2html.py from Docutils, since it's a > duplicate of what's in Python's CVS. Ah, thank you. > BTW, we should do another Bug Day soon, especially if others could > join in. Good idea. I'd be happy to join. Unfortunately, I'm away from 2004-09-20 (next Monday) to 2004-09-24 (Friday), and from 2004-10-03 (Sunday) to 2004-10-15 (Friday). It would be good if we could find a day outside these time spans (but I wouldn't mind if we can't). Maybe start a new bug-day thread for coordination? > It would be more fun if it weren't just Felix & me. Indeed. -- When replying to my email address, please ensure that the mail header contains 'Felix Wiemann'. http://www.ososo.de/ |
|
From: David G. <go...@py...> - 2004-09-16 20:49:05
|
2004-07-27 Docutils Bug Day IRC transcript: http://docutils.sf.net/misc/20040727_bug_day.txt It's not in CVS (should it be?). [David Goodger] >> BTW, we should do another Bug Day soon, especially if others could >> join in. [Felix Wiemann] > Maybe start a new bug-day thread for coordination? Done. Who'd like to join in the Second Official Docutils Bug Day? When is convenient? -- David Goodger <http://python.net/~goodger> |
|
From: Felix W. <Fel...@gm...> - 2004-09-17 16:51:42
|
David Goodger wrote: > 2004-07-27 Docutils Bug Day IRC transcript: > http://docutils.sf.net/misc/20040727_bug_day.txt Thank you. > It's not in CVS (should it be?). I don't think it needs to be under version control. > Who'd like to join in the Second Official Docutils Bug Day? > When is convenient? Generally, Friday and Saturday are best for me. As I mentioned before, I'm away from 2004-09-20 to 2004-09-24 and from 2004-10-03 to 2004-10-15. The following days in September and October would be most convenient: 2004-09-25 (Saturday) (not very much preparation time) 2004-10-01 (Friday) (only part of the day) 2004-10-16 (Saturday) (not very much preparation time) 2004-10-22 (Friday) (only part of the day) 2004-10-23 (Saturday) 2004-10-29 (Friday) 2004-10-30 (Saturday) But I might be able to take part for some time on other days, too. Maybe it would be good if some users/developers with special or unusual usages of Docutils were also there? I'm not sure, but it might be helpful for discovering special requirements or problems. Should we also ask for bug *reports* to get some new reports we wouldn't get otherwise? -- When replying to my email address, please ensure that the mail header contains 'Felix Wiemann'. http://www.ososo.de/ |
