Hi Danek,
My replies embedded:
-manjunath
Danek Duvall wrote:
> Mark Carlson wrote:
>
>
>> Dependencies
>> ============
>>
>> SUNWpython {Python core package, already available on opensolaris }
>> - This is must have dependency.
>>
>> SUNWcherry-python {Web framework for Python, available on opensolaris }
>> - Routes can work with other web frameworks as well, but this is what I
>> have used for testing.
>>
>
> There are no packages "SUNWpython" or "SUNWcherry-python". There are
> "SUNWPython", "SUNWPython26", and "SUNWpython-cherrypy". The last of those
> is a project-private implementation detail of pkg(5) (PSARC/2008/190), and
> hasn't been approved by an ARC to be delivered in the Solaris WOS as a
> stand-alone component.
>
>
I will list the following dependencies:
SUNWPython at 2.4.4,5.11-0.111:20090508T152730Z
SUNWPython26 at 2.6.1,5.11-0.111:20090508T152901Z
SUNWpython-cherrypy at 3.1.1,5.11-0.111:20090508T163103Z
> If the web engine is pluggable, is it appropriate to have a hard dependency
> on one of them?
>
But, routes would not work without some version of python, either
2.4 or 2.6. That is the only hard dependency. CherryPy, is not a
hard dependency.
> If you're delivering both Python 2.4 and Python 2.6 modules in the same
> package, which version of Python does the package depend on?
>
>
Ok, agreed. I will deliver the following two packages:
SUNWpython24-routes
SUNWpython26-routes
>> Interfaces
>> ==========
>>
>> Man pages are included.
>>
>> The SUNWpy-routes package is Uncommitted.
>>
>> The remaining interfaces are Volatile.
>>
>> Exported Interfaces
>> -------------------
>> None
>>
>
> None? At all? If a project exports no interfaces, then there's no
> architectural content.
>
I thought, since we are just exposing modules and classes to a web
framework,
they are not public interfaces...it becomes an active exposed interface if
an instance of a class is created, I thought..
Ok, here are the interfaces or modules exposed to any python web framework:
routes
Provides common classes and functions most users will want access to.
routes.base
Route and Mapper core classes
routes.middleware
Routes WSGI Middleware
routes.threadinglocal
routes.util
Utility functions for use in templates / controllers
>
>> Imported Interfaces
>> -------------------
>> None
>>
>
>
Again, routes imports some modules and classes from Cherrypy...
> Again?
>
>
>> Not An Interface
>> --------------------
>> /usr/lib/python2.6/vendor-packages/Routes-1.10.3-py2.6.egg-info/PKG-INFO
>> /usr/lib/python2.6/vendor-packages/Routes-1.10.3-py2.6.egg-info/SOURCES.txt
>> /usr/lib/python2.6/vendor-packages/Routes-1.10.3-py2.6.egg-info/dependency.txt
>> /usr/lib/python2.6/vendor-packages/Routes-1.10.3-py2.6.egg-info/not-zip-safe
>> /usr/lib/python2.6/vendor-packages/Routes-1.10.3-py2.6.egg-info/top_level.txt
>> /usr/lib/python2.6/vendor-packages/routes/__init__.py
>> /usr/lib/python2.6/vendor-packages/routes/base.py
>> /usr/lib/python2.6/vendor-packages/routes/mapper.py
>> /usr/lib/python2.6/vendor-packages/routes/middleware.py
>> /usr/lib/python2.6/vendor-packages/routes/route.py
>> /usr/lib/python2.6/vendor-packages/routes/threadinglocal.py
>> /usr/lib/python2.6/vendor-packages/routes/util.py
>>
>
> Everything you're delivering is not an interface?
>
> Danek
>
Again, I am not sure what is the definition of an interface...what
routes does
is, it provides a set of Modules and classes for programmers to develop
mapping between URLs and actions...for implementing dynamic web
applications..
Please do correct me if I am wrong..
-manjunath
