Request for comment about : move DAV and DAVServer to pywebdav namespace, split pywebdav into two packages

[GoogleCodeExporter]

Hi,

currently, PyWebDAV use two namespaces :

* DAV
* DAVServer

I suggest to move this two namespaces to "pywebdav".

Then, we'll have :

* pywebdav.DAV
* pywebdav.Server

Well, I think "DAV" namespace isn't well-adapted. I suggest this :

pywebdav.lib
pywebdav.server

I've planned to append wsgi support, then I suggest this modules files names :

pywebdav/lib/wsgi_webdav…app.py
pywebdav/lib/webdav_http_request_handler.py

Actual "WebDAVServer.py" file would be renamed to
"webdav_http_request_handler.py".

Other proposition : if one developer don't want server script but he want
only use wsgi webdav app in her application, there would perfect if he can
install only pywebdav.lib package without pywebdav.server part !

Then, I suggest to split pywebdav to two packages : 

pywebdav.lib
pywebdav.server

What do you think about all this suggests ?

Thanks for your comment,
Regards,
Stephane

Original issue reported on code.google.com by klein.stephane on 4 Aug 2009 at 8:45

[GoogleCodeExporter]

I don't think we should split pywebdav into 2 packages. pywebdav is small so 
having 
both server and lib is not really space consuming.
For the name of the files, I would prefer to use CamelCase naming.
Otherwise I agree to put all under the pywebdav namespace.
I'm not sure about the server and lib subdirectory, I think we should do like 
Python 
for HTTPServer (BaseHTTPServer, CGIHTTPServer, SimpleHTTPServer).

Original comment by cedric.krier@b2ck.com on 16 May 2010 at 1:28

[GoogleCodeExporter]

+1 for lib and server in package pywebdav - will perform these changes in trunk

Original comment by spamsch@gmail.com on 12 Feb 2011 at 8:31

• Changed state: Fixed