Changes between Version 4 and Version 5 of PyYAMLLegacy

Timestamp:

03/11/06 17:13:36 (7 years ago)

Author:

xi

Comment:

--

PyYAMLLegacy

@@ -16 +16 @@
 == Documentation ==
 
-The documentation will consist of two major levels. User documentation (i.e. python developers using PyYAML) and PyYAML developers.
-
  * LegacyUserDocumentation
- * LegacyDeveloperDocumentation
 
 == Subversion Repository ==
@@ -71 +68 @@
 For the moment, additional/temporary notes about commits that can be added in LegacyChangesetNotes.
 
+= Notes =
+
+A place to dump found information before formatting into the wiki
+
+  * LegacySavingClassInstances
+  * LegacyRoundTripping
+  * An LegacyPythonToDo
+  * LegacyTempNotes
+  * LegacyMikeOrrsPage
+
+= History =
+
+From [http://yaml.kwiki.org yaml.kwiki.org]
+
+ * March 2002 - Steve Howell starts work on parser only
+ * April 2002 - no progress
+ * May 2002 - no progress
+ * June 2002 - Steve Howell begins work on the project again, gets a little help from Ryan King, and gets a basic emitter working, along with a few more cases for the parser
+   * SlideShowell - first PyYAML application
+ * July 2002 - Clark Evans and Steve Howell add major features:
+   * distutils setup
+   * catch up to flurry of spec changes from late Spring
+   * better parser compliance
+   * alias support for the emitter
+   * YAML is fully bootstrapped – test cases are YAML-driven (see LegacyTestingSuite)
+   * Clark Evans begins support for YPATH and queries (with some help from Steve Howell)
+ * August 2002 - Dave Kuhlman joins the project
+   * better support for serializing objects
+   * !XmlYaml (XML to/from YAML mappings)
+   * dumpTo**File method
+   * started to spike some ideas for pull parser and schemas
+ * September 2002 - way too much time on the mailing list
+   * starting to clean up flow collections loading
+   * reoranizing code a bit to prepare for more flexible implicit handling
+   * giving talk to DC Python users group, using SlideShowell (9/21)
+   * bug fixing