Changeset 77


Ignore:
Timestamp:
07/10/04 08:02:48 (9 years ago)
Author:
tim
Message:

added tests folder

Location:
trunk
Files:
1 added
4 edited

Legend:

Unmodified
Added
Removed
  • trunk/CHANGELOG

    r76 r77  
    44  changes: 
    55    - yaml.file() 
     6    - unit tests for all tests 
    67--- 
    78- version: 0.32 
  • trunk/LIMITATIONS

    r71 r77  
    11PYTHON VERSION: > 
    2    PyYaml is developed with Python version 2.2.  I can't live  
    3    without Python 2.2--too many great features.  Please do  
    4    yourself a favor and upgrade now.  I know the decision to 
    5    only support 2.2 and above may lock out some potential users, 
    6    but I believe it will pay dividends in the future, because 
    7    the version 2.2 features allow cleaner and more expressive  
    8    code.  I do intend to support version 2.2 for a long time. 
     2   PyYaml is now being develioed on version 2.3. If version 2.2 is needed 
     3   we're happy to look at the nescessities. There won't be unjustified  
     4   uses of 2.3 if possible although at some point it's likely. Keep watching 
     5   for further news 
    96 
    107DISCLAIMER: >  
    118   PyYaml is not ready to be used as a robust serialization tool, 
    129   although it is moving in that direction, and you can certainly 
    13    experiment with it. 
     10   experiment with it. This sentence may still be true? 
    1411 
    1512   You can use it more safely for one-way applications.  You can 
     
    1815   tool, for things like logging and debugging. 
    1916 
    20    You can report bugs to showell@zipcon.net.  As of this writing 
    21    (August 2002), I am actively improving PyYaml. 
    22  
    23    The interface for YAML is stabilizing, but it is too early in  
    24    the life cycle for me to guarantee backward compatibility in  
    25    future releases.  I recommend wrapping your YAML calls in your  
    26    own methods, if you are concerned about changing interfaces. 
    27    The basic paradigm of load, loadFile, save, and saveFile  
    28    shouldn't change, but the way that you customize the loader  
    29    and parser's behavior may. 
     17   You can report bugs on http://pyyaml.dnsalias.org or through 
     18   lists.pollenation.dnsalias.org/mailman/listinfo/pyyaml. 
    3019 
    3120SOME KNOWN BUGS/LIMITATIONS: 
     21  These will be reveiwed (TP JUL 04) 
     22 
    3223  - folded scalars can't lead with blank line 
    3324  - emitter gives invalid YAML for multi-line scalars starting w/whitespace 
  • trunk/TESTING

    r71 r77  
    55setting this up. 
    66 
    7 When you check code out of Perforce, please set up your client 
    8 to check out TestingSuite as a subfolder of PyYaml. 
    9  
    10 Thanks, 
    11  
    12 Steve 
     7As of July 2004, Testing will be moving to a tests directory. profileYaml.py is currently runs the TestingSuite 
  • trunk/profileYaml.py

    r71 r77  
    1616            for subDoc in yaml.load(doc['yaml']): 
    1717                pass 
    18 print dir(profile) 
     18 
    1919profile.run('loadAllFiles()', 'profileResults') 
    2020 
Note: See TracChangeset for help on using the changeset viewer.