search

eftsung / pygr

Automatically exported from code.google.com/p/pygr
0 stars 0 forks source link

Refactor top-level pygr.Data namespace access #58

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
We've had several discussions about changing how top-level names should be
accessed from pygr.Data.  For one example thread, see
http://groups.google.com/group/pygr-dev/browse_thread/thread/252715d4d0dc2120/90
cc8c5e60488d3b?lnk=gst&q=namespace#90cc8c5e60488d3b
or
http://groups.google.com/group/pygr-dev/browse_thread/thread/855a0087d00fbabe

The question is: make a simple change right now, or wait to do this as part
of a larger reorganization / extension of pygr.Data (tentatively planned
for release 1.0)?

Original issue reported on code.google.com by cjlee...@gmail.com on 7 Jan 2009 at 4:58

GoogleCodeExporter commented 8 years ago 
this was done as part of the metabase refactoring.

Original comment by cjlee...@gmail.com on 25 Mar 2009 at 7:53

GoogleCodeExporter commented 8 years ago 
Committed to master, no?

Original comment by the.good...@gmail.com on 26 Apr 2009 at 8:52