That sounds a bit excessive. Is there a recent incident that inspired this proposal? On Wed, Nov 29, 2017 at 10:26 AM, Serhiy Storchaka <storchaka at gmail.com> wrote: > After removing files from the repository they disappear from the source > tree, and it is even hard to notice this if you don't use it regularly. It > is hard to track the history of the removed file even if you know it exact > path. If you know it only approximate this is harder. > > I think that any file removals from the repository should pass some > PEP-like process. Declaring the intention with the rationale, taking a > feedback, discussing, and finally documenting the removal. Perhaps it is > worth to track all removals in a special file, so if later you will find > that the removed file can be useful you could restore it instead of > recreating its functionality from zero in the case if you even don't know > that similar file existed. > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido% > 40python.org > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171129/043fc05a/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4