-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Rename rst peps to .rst
#39
Conversation
simply ```ipython files = ! ls *.txt for name in files: with open(name) as f: if 'Content-Type: text/x-rst' in f.read(): !git mv {name} {name[:-3]}rst ```
Thanks! Yes, this will definitely break python.org :) I have a WIP branch that fixes a couple issues with the PEP importer. I can tweak it look for |
I've marked this PR as a work-in-progress until the python.org side is dealt with. |
Sure, if you want a cleaner PR queue, feel free to close, we can reopen when time is right. |
Is there an issue or PR for the pydotorg side of things that we can track in regards to this PR? |
No, I was planning to fix it (also hg.python.org links needs to be updated) while working on python/pythondotorg#825 :) |
Note that PEP preambles are not in valid reST format. Would it break PEP processing tools if they are converted to reST comments (.. directive) or pre-formatted text (:: directive)? |
@abalkin yes, they would break. Eventually the headers would need to be changed to be valid reST, but one thing at a time. 😄 |
Closing to keep things clean, it's easy to redo. |
Add myself (Joshua) to the authors list
Not sure how many things that would break when pushing on pythondotorg. That's pretty easy to redo if it's not the right time.