Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Move peps into subdirectory #10
Closed
Labels
Projects
Comments
timofurrer
added a commit
to timofurrer/peps
that referenced
this issue
Jun 17, 2016
This change moves all PEPs into the `peps/` subdirectory. The HTML files generated by `pep2html.py` will be located in `output/`. The `make` to convert a single PEP to HTML change slightly **if** you specify the path. It's still the when specifying the id. From: `make pep-0020.txt` To: `make peps/pep-0020.txt` ... just use tab completion ;)
timofurrer
added a commit
to timofurrer/peps
that referenced
this issue
Jun 17, 2016
This change moves all PEPs into the `peps/` subdirectory. The HTML files generated by `pep2html.py` will be located in `output/`. The `make` to convert a single PEP to HTML change slightly **if** you specify the path. It's still the when specifying the id. From: `make pep-0020.txt` To: `make peps/pep-0020.txt` ... just use tab completion ;)
timofurrer
added a commit
to timofurrer/peps
that referenced
this issue
Jun 17, 2016
This change moves all PEPs into the `peps/` subdirectory. The HTML files generated by `pep2html.py` will be located in `output/`. The `make` command to convert a single PEP to HTML has changed slightly **if** you specify the path. It's still same the when specifying the id. From: `make pep-0020.txt` To: `make peps/pep-0020.txt` ... just use tab completion ;)
|
So I think we shouldn't move files around because it'll mean that we can't view the complete file history on GitHub. |
|
Yep, unfortunately the move will break stuff, so I will close this. |
|
I wonder if changing the website field in the repo description to be |
|
Sigh. When will it be easy to do things that are obviously desirable? I sit
here in front of my top-of-the-line Map Pro thinking that in 100 years, if
the human race has survived, they will think of me much as I think of the
early humans who painted on cave walls and fashioned tools from flint. S
…On Tue, Nov 21, 2017 at 8:36 PM, Éric Araujo ***@***.***> wrote:
I wonder if changing the website field in the repo description to be
#python-enhancement-proposals or https://github.com/python/
peps#python-enhancement-proposals would help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAGbYEkXNpd0uBecV1zGb4ugbqFef6nzks5s4zQxgaJpZM4I3BVW>
.
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
|
trishankatdatadog
added a commit
to lukpueh/peps
that referenced
this issue
Oct 10, 2019
Update images to show bin N
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The root directory listing is currently very long, which means that nobody will see github's readme rendering.
The peps sources could be moved into a subdirectory, separated from the scripts used to generate the rendered versions.
The text was updated successfully, but these errors were encountered: