Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Python: Bugs

[issue14215] http://www.python.org/dev/peps/ title is python.org

 

 

Python bugs RSS feed   Index | Next | Previous | View Threaded


report at bugs

Jun 4, 2012, 6:46 AM

Post #1 of 7 (104 views)
Permalink
[issue14215] http://www.python.org/dev/peps/ title is python.org

Ramchandra Apte <maniandram01 [at] gmail> added the comment:

What it the status of this bug?

----------

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue14215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com


report at bugs

Jun 4, 2012, 6:50 AM

Post #2 of 7 (102 views)
Permalink
[issue14215] http://www.python.org/dev/peps/ title is python.org [In reply to]

R. David Murray <rdmurray [at] bitdance> added the comment:

Presumably the PEP 0 generator needs a patch, but that's not something most of us ever touch. I've added Nick to nosy, I think he made changes to it last.

----------
nosy: +ncoghlan, r.david.murray

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue14215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com


report at bugs

Jun 16, 2012, 10:41 PM

Post #3 of 7 (90 views)
Permalink
[issue14215] http://www.python.org/dev/peps/ title is python.org [In reply to]

Nick Coghlan <ncoghlan [at] gmail> added the comment:

This is actually related to the integration between the PEP formatting tools and the python.org build system (that is, pep2pyramid.py, rather than genpepindex.py)

I'm inclined to close it as "won't fix" and maybe pass it to the psf-redesign list to look into as part of the python.org RFP.

----------
nosy: +michael.foord

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue14215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com


report at bugs

Jun 17, 2012, 5:16 AM

Post #4 of 7 (92 views)
Permalink
[issue14215] http://www.python.org/dev/peps/ title is python.org [In reply to]

Michael Foord <michael [at] voidspace> added the comment:

As the PEPs are "development docs", like the Python documentation itself, I wouldn't have *expected* it to be covered by the redesign. Does this require anything more than an update to the PEP index template?

----------

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue14215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com


report at bugs

Jun 17, 2012, 5:30 AM

Post #5 of 7 (94 views)
Permalink
[issue14215] http://www.python.org/dev/peps/ title is python.org [In reply to]

Nick Coghlan <ncoghlan [at] gmail> added the comment:

I'm expecting the "pep2pyramid.py" part to change at the very least.

However, back on topic, I actually hit the limits of my knowledge of the PEP build process reading that script.

As near as I can tell, PEP 0 should have the same "title" information as is available for the other PEPs. It does appear the individual PEPs and the index do use differently templates though, so that may be the source of the discrepancy.

----------

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue14215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com


report at bugs

Jun 17, 2012, 5:46 AM

Post #6 of 7 (90 views)
Permalink
[issue14215] http://www.python.org/dev/peps/ title is python.org [In reply to]

Ezio Melotti <ezio.melotti [at] gmail> added the comment:

The title for the PEPs seem to be set in the fixfile function, at the line 206.

Maybe something like:
if pep:
title = "PEP " + pep + " -- " + title
else:
title = "PEP index"
works, assuming that only title-less page is the index.

----------
nosy: +ezio.melotti

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue14215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com


report at bugs

Jun 17, 2012, 1:13 PM

Post #7 of 7 (91 views)
Permalink
[issue14215] http://www.python.org/dev/peps/ title is python.org [In reply to]

Nick Coghlan <ncoghlan [at] gmail> added the comment:

As near as I can tell, pep will hold the string value "0" for the PEP index, thus the title should still be getting set. That's why I suspect a templating difference.

----------

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue14215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

Python bugs RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.