[pygr-notify] Issue 134 in pygr: UCSCEnsemblInterface fails with Genome doesn't exist error

[pygr at googlecode.com]

Updates:
	Owner: cjlee... at gmail.com

Comment #1 on issue 134 by mare... at gmail.com: UCSCEnsemblInterface fails  
with Genome doesn't exist error
http://code.google.com/p/pygr/issues/detail?id=134

This is definitely a useful change and one worth keeping, in case of future  
changes to the UCSC database which could make hitherto-unique rows lose  
their uniqueness. However, IMHO we need a bit more here before this issue  
can be closed - namely, it may make sense to actually choose among the  
returned rows. Two options (which could be combined) spring to mind:
  - choosing the latest Ensembl-dataset version available for the specified  
UCSC genome,
  - letting the user specify the Ensembl version as well.