Closed Xerez13 closed 8 years ago
Hey @Xerez13,
Thanks for this detailed report. I'm not, however, able to reproduce the problem! In the most recent master branch of pyensembl, line 99 of database.py
is:
['transcript_name'],
and the expression datacache.db.db_table_exists
doesn't occur anywhere in the file.
Any chance you're using an older version of pyensembl
with a more recent datacache
?
Hey @iskandr ,
I just checked and I am using pyensembl-0.5.4 which appears to be an older version of the package. My datacache version is 0.4.16. It is likely this error comes about exactly for the reason you suggest.
i had the same issue..datacache-0.4.16-py2.7.egg, pyensembl-0.5.4-py2.7.egg
Hey Rohan,
Can you try upgrading your version of PyEnsembl to the more recent 0.8.4?
On Sun, Feb 14, 2016 at 5:58 PM, Rohan Gnanaolivu notifications@github.com wrote:
i had the same issue..datacache-0.4.16-py2.7.egg, pyensembl-0.5.4-py2.7.egg
— Reply to this email directly or view it on GitHub https://github.com/hammerlab/pyensembl/issues/133#issuecomment-183998439 .
I'm going to close since I suspect this error only occurs when an older PyEnsembl is installed with a newer datacache.
I recently installed and ran pyensembl on my machine. The first time I called the module in an interactive session everything worked great.
However, in any subsequent calls, typing in the same code as above, I received the following error:
When I went to the
_connect_or_create_database
function within database.py I found the following line was throwing the error:When I looked at the module datacache I found neither the db nor db_table_exists function:
My version of datacache was 0.4.16
The line which throws the error appears to be calling a functionality which is not present in datacache. The code initially works fine because if db_path does not exist the function directs to _create_database() which contains functions present in datacache. However, in subsequent calls the function attempts to execute the troublesome line and throws the error. I was able to get around this error by commenting out the line in question along with the return statement below it. I inserted a return statement below the db assignment. A copy of my adjustment is shown below.
I just thought I would raise this issue since this tool is quite cool and has great functionality, but this error might frustrate people if they aren't willing to investigate it.