Added copyright

Author: TobiasWrigstad

peps/pep-0795.rst

@@ -2183,7 +2183,7 @@ careful design considerations.
 
 
 Equality of immutable objects
--------------------------------
+-----------------------------
 
 One consideration with the naive approach (i.e., hash via id()) is that
 it can result in confusing outcomes. For example, if there were to be
@@ -2203,7 +2203,7 @@ recommended in order to avoid this behavior.
 
 
 Types
-======
+=====
 
 Support for immutability in the type system is worth exploring in the
 future.
@@ -2230,7 +2230,7 @@ consider for the future in conjunction with work on typing immutability.
 
 
 Data-race free Python
-======================
+=====================
 
 This PEP adds support for immutable objects to Python and importantly
 permits sub-interpreters to directly share *immutable* objects. As a
@@ -2287,7 +2287,7 @@ do not at this moment provide the decorators (*e.g.*, ``@frozen``) at present, t
 they are trivial to implement using the existing tools and functionality.
 
 Open questions to resolve before publishing
-############################################
+###########################################
 
 - Do we cover C extensions enough?
 - Do we need a separate discussion about backwards compatibility?
@@ -2298,6 +2298,12 @@ Open questions to resolve before publishing
 - Need an example that shows sharing across sub-interpreters
 
 Feedback to address
-====================
+===================
 - Use tp_traverse to traverse, or add a new type operation that
   is required for freezable types?
+
+
+Copyright
+#########
+
+This document has been placed in the public domain.