Proposed short-term changes to pygr.Data (for 0.8) - no more connecting to resource databases during import
- create a root object that acts as the root of the data namespace, either in pygr.Data or pygr.__init__ - by analogy to sys.path (an interface to PYTHONPATH), create a pygr.Data.path object that acts as a list of the resource databases (an interface to PYGRDATAPATH). - stop using "layer names" (such as "my", "here", etc.) to specify where to save a given resource. Instead, users can access a desired resource database from the list in pygr.Data.path, or create / open a new resource database by calling an appropriate constructor. The interface for saving to a specific resource database object will be the same as the generic interface. - split the ResourceFinder class into separate pieces for storing the list of resource databases (described above as pygr.Data.path); the cache of currently loaded resources; the queue of resources that the user has queued for saving but not yet committed. Please send me any comments you have; we can also discuss this in the developer conference call today. -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
