[TransWarp] Testing Help Needed: URL contexts

alexander smishlajev alex at ank-sia.com
Mon May 19 15:13:38 EDT 2003

Phillip J. Eby wrote:
> I just checked in a replacement for the old URL parsing mechanisms in 
> PEAK, and I could really use some help with validating that the existing 
> supported schemes are parsed correctly by the current CVS version of 

FileURL does incorrectrly handle relative paths.

> If you can supply examples of URLs that produce parse failures, 
> incorrect resulting field values, or incorrect formatting of a parsed 
> URL, please send them to me via the list, preferably in the form of 
> additions to the test suite.

RCS file: /cvsroot/PEAK/src/peak/naming/tests/__init__.py,v
retrieving revision 1.16
diff -u -r1.16 __init__.py
--- __init__.py	2003/05/18 16:20:35	1.16
+++ __init__.py	2003/05/19 19:07:32
@@ -64,6 +64,18 @@
          Items(scheme='logfile', path=('','foo','bar'), level=30),

+    'logfile:spam?level=WARNING':
+        Items(scheme='logfile', path=('spam'), level=30),
+    'logfile:./egg?level=WARNING':
+        Items(scheme='logfile', path=('.','egg'), level=30),
+    'logfile://beacon?level=WARNING':
+        Items(scheme='logfile', path=('beacon'), level=30),
+    'logfile://./sausage?level=WARNING':
+        Items(scheme='logfile', path=('.','sausage'), level=30),
          Items(scheme='win32.dde', service='foo', topic='bar', 
                retries=24, sleep=42),

the first two examples are formatted differently from original source 
(formatting always adds "//" after the scheme component), but i am not 
sure if this may be called "incorrect formatting" since the url meaning 
does not change.

best wishes,

More information about the PEAK mailing list