Move peps into subdirectory

[birkenfeld]

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.

[Mariatta]

So I think we shouldn't move files around because it'll mean that we can't view the complete file history on GitHub.

[brettcannon]

Yep, unfortunately the move will break stuff, so I will close this.

[merwok]

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.

[holdenweb]

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/

[pradyunsg]

I'll reopen this since the reasons that was originally rejected due to are no longer applicable:

• the lack of git log --follow functionality on GitHub: it now exists. The loss of history navigability on the GitHub is no longer a thing.
• the build system is also independent of pythondotorg now.

So, such a move will no longer break things as it would have in 2017, and this can be reconsidered.

[encukou]

Is the README that important here? There's short description that could fit in GH's repo description, a link to Contributing Guidelines and a few things that probably should be moved to Contributing Guidelines.

[pradyunsg]

FWIW, this isn't just about the README at this point -- it'll also make it clearer what is "PEP sources" vs the supporting infrastructure around them. We have a non-trivial amount of supporting code and documents around PEPs living in the same repository currently, and moving PEP sources (+ supporting images etc) into a distinct folder will create a separation that would be useful.

Whether the benefits are worth the transition costs is the main question IMO -- I think it is, which is why I've reopened this and suggested that this be reconsidered. :)