How to verify a locally installed version of a module is the one used by pip?









up vote
1
down vote

favorite












I have manually installed datatable (from h2o.ai) https://github.com/h2oai/datatable from HEAD of master



 make build
 make install


They were successful. However when running pip3 freeze I see the (v old) default version (0.6.0) that had been installed via



pip3 install datatable


some months back:



$pip3 freeze | grep datatable

datatable==0.6.0


I am uncertain whether:



  • the locally built version of datatable is not being used

  • the locally built version of datatable is being used but not reported by pip3

    • if that were the case: how to verify the locally built/installed version were being used (or not)


Tips appreciated.



Updates



Based on (great) comments below:



import datatable then print(datatable.__version__)

 0.6.0


But the datatable.__file__ shows the local version:



In [3]: print(datatable.__file__)
/git/datatable/datatable/__init__.py


Does this possibly mean that the local installation is being used - but that the version reported by that locally built one is still the same (v old) one that was published to pip repositories months earlier?






python pip







share|improve this question



















  • 1




    why not import datatable then print(datatable.__version__). Try dir(datatable) to make sure there's a version attribute in there.
    – duhaime
    Nov 10 at 20:13











  • use a virtualenv
    – Corey Goldberg
    Nov 10 at 20:13










  • I will try that .. but there is no general way to find a version (not all libraries export that identifier __version__).: I'd like to know the answer not just for this particular library
    – javadba
    Nov 10 at 20:14










  • Looking at Makefile this local build was installed with pip (python2.7) I guess that's why it is not visible for pip3. Try if pip freeze will show correct version.
    – Raoslaw Szamszur
    Nov 10 at 20:15







  • 2




    Better, use datatable.__file__ - that will show the location of the imported file
    – duhaime
    Nov 10 at 20:17














up vote
1
down vote

favorite












I have manually installed datatable (from h2o.ai) https://github.com/h2oai/datatable from HEAD of master



 make build
 make install


They were successful. However when running pip3 freeze I see the (v old) default version (0.6.0) that had been installed via



pip3 install datatable


some months back:



$pip3 freeze | grep datatable

datatable==0.6.0


I am uncertain whether:



  • the locally built version of datatable is not being used

  • the locally built version of datatable is being used but not reported by pip3

    • if that were the case: how to verify the locally built/installed version were being used (or not)


Tips appreciated.



Updates



Based on (great) comments below:



import datatable then print(datatable.__version__)

 0.6.0


But the datatable.__file__ shows the local version:



In [3]: print(datatable.__file__)
/git/datatable/datatable/__init__.py


Does this possibly mean that the local installation is being used - but that the version reported by that locally built one is still the same (v old) one that was published to pip repositories months earlier?






python pip







share|improve this question



















  • 1




    why not import datatable then print(datatable.__version__). Try dir(datatable) to make sure there's a version attribute in there.
    – duhaime
    Nov 10 at 20:13











  • use a virtualenv
    – Corey Goldberg
    Nov 10 at 20:13










  • I will try that .. but there is no general way to find a version (not all libraries export that identifier __version__).: I'd like to know the answer not just for this particular library
    – javadba
    Nov 10 at 20:14










  • Looking at Makefile this local build was installed with pip (python2.7) I guess that's why it is not visible for pip3. Try if pip freeze will show correct version.
    – Raoslaw Szamszur
    Nov 10 at 20:15







  • 2




    Better, use datatable.__file__ - that will show the location of the imported file
    – duhaime
    Nov 10 at 20:17












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have manually installed datatable (from h2o.ai) https://github.com/h2oai/datatable from HEAD of master



 make build
 make install


They were successful. However when running pip3 freeze I see the (v old) default version (0.6.0) that had been installed via



pip3 install datatable


some months back:



$pip3 freeze | grep datatable

datatable==0.6.0


I am uncertain whether:



  • the locally built version of datatable is not being used

  • the locally built version of datatable is being used but not reported by pip3

    • if that were the case: how to verify the locally built/installed version were being used (or not)


Tips appreciated.



Updates



Based on (great) comments below:



import datatable then print(datatable.__version__)

 0.6.0


But the datatable.__file__ shows the local version:



In [3]: print(datatable.__file__)
/git/datatable/datatable/__init__.py


Does this possibly mean that the local installation is being used - but that the version reported by that locally built one is still the same (v old) one that was published to pip repositories months earlier?






python pip







share|improve this question















I have manually installed datatable (from h2o.ai) https://github.com/h2oai/datatable from HEAD of master



 make build
 make install


They were successful. However when running pip3 freeze I see the (v old) default version (0.6.0) that had been installed via



pip3 install datatable


some months back:



$pip3 freeze | grep datatable

datatable==0.6.0


I am uncertain whether:



  • the locally built version of datatable is not being used

  • the locally built version of datatable is being used but not reported by pip3

    • if that were the case: how to verify the locally built/installed version were being used (or not)


Tips appreciated.



Updates



Based on (great) comments below:



import datatable then print(datatable.__version__)

 0.6.0


But the datatable.__file__ shows the local version:



In [3]: print(datatable.__file__)
/git/datatable/datatable/__init__.py


Does this possibly mean that the local installation is being used - but that the version reported by that locally built one is still the same (v old) one that was published to pip repositories months earlier?






python pip




python pip






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 10 at 20:22

























asked Nov 10 at 20:06









javadba

21.1k31141276




21.1k31141276







  • 1




    why not import datatable then print(datatable.__version__). Try dir(datatable) to make sure there's a version attribute in there.
    – duhaime
    Nov 10 at 20:13











  • use a virtualenv
    – Corey Goldberg
    Nov 10 at 20:13










  • I will try that .. but there is no general way to find a version (not all libraries export that identifier __version__).: I'd like to know the answer not just for this particular library
    – javadba
    Nov 10 at 20:14










  • Looking at Makefile this local build was installed with pip (python2.7) I guess that's why it is not visible for pip3. Try if pip freeze will show correct version.
    – Raoslaw Szamszur
    Nov 10 at 20:15







  • 2




    Better, use datatable.__file__ - that will show the location of the imported file
    – duhaime
    Nov 10 at 20:17












  • 1




    why not import datatable then print(datatable.__version__). Try dir(datatable) to make sure there's a version attribute in there.
    – duhaime
    Nov 10 at 20:13











  • use a virtualenv
    – Corey Goldberg
    Nov 10 at 20:13










  • I will try that .. but there is no general way to find a version (not all libraries export that identifier __version__).: I'd like to know the answer not just for this particular library
    – javadba
    Nov 10 at 20:14










  • Looking at Makefile this local build was installed with pip (python2.7) I guess that's why it is not visible for pip3. Try if pip freeze will show correct version.
    – Raoslaw Szamszur
    Nov 10 at 20:15







  • 2




    Better, use datatable.__file__ - that will show the location of the imported file
    – duhaime
    Nov 10 at 20:17







1




1




why not import datatable then print(datatable.__version__). Try dir(datatable) to make sure there's a version attribute in there.
– duhaime
Nov 10 at 20:13





why not import datatable then print(datatable.__version__). Try dir(datatable) to make sure there's a version attribute in there.
– duhaime
Nov 10 at 20:13













use a virtualenv
– Corey Goldberg
Nov 10 at 20:13




use a virtualenv
– Corey Goldberg
Nov 10 at 20:13












I will try that .. but there is no general way to find a version (not all libraries export that identifier __version__).: I'd like to know the answer not just for this particular library
– javadba
Nov 10 at 20:14




I will try that .. but there is no general way to find a version (not all libraries export that identifier __version__).: I'd like to know the answer not just for this particular library
– javadba
Nov 10 at 20:14












Looking at Makefile this local build was installed with pip (python2.7) I guess that's why it is not visible for pip3. Try if pip freeze will show correct version.
– Raoslaw Szamszur
Nov 10 at 20:15





Looking at Makefile this local build was installed with pip (python2.7) I guess that's why it is not visible for pip3. Try if pip freeze will show correct version.
– Raoslaw Szamszur
Nov 10 at 20:15





2




2




Better, use datatable.__file__ - that will show the location of the imported file
– duhaime
Nov 10 at 20:17




Better, use datatable.__file__ - that will show the location of the imported file
– duhaime
Nov 10 at 20:17












1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










To look precisely at the module being used, the best way, as mentioned by @duhaime is to use import datatable; print(datatable.__file__).



If your local installation was done correctly, then you should also make sure that 1) the location where you installed it is in your PYTHONPATH, 2) that if it is, the path is placed before that of the standard paths (lookup is sequential).
An easy way to check that it is in the path if you don't know where to look is just to uninstall the version installed through pip.



EDIT



Based on the edit to the question, yes, the version is still the same (see here)






share|improve this answer




















  • I am going to update the version to 0.6.5 in my local git clone
    – javadba
    Nov 10 at 20:27











  • $ipython -c "import datatable; print(datatable.__version__)" 0.6.5
    – javadba
    Nov 10 at 20:31











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242959%2fhow-to-verify-a-locally-installed-version-of-a-module-is-the-one-used-by-pip%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










To look precisely at the module being used, the best way, as mentioned by @duhaime is to use import datatable; print(datatable.__file__).



If your local installation was done correctly, then you should also make sure that 1) the location where you installed it is in your PYTHONPATH, 2) that if it is, the path is placed before that of the standard paths (lookup is sequential).
An easy way to check that it is in the path if you don't know where to look is just to uninstall the version installed through pip.



EDIT



Based on the edit to the question, yes, the version is still the same (see here)






share|improve this answer




















  • I am going to update the version to 0.6.5 in my local git clone
    – javadba
    Nov 10 at 20:27











  • $ipython -c "import datatable; print(datatable.__version__)" 0.6.5
    – javadba
    Nov 10 at 20:31















up vote
1
down vote



accepted










To look precisely at the module being used, the best way, as mentioned by @duhaime is to use import datatable; print(datatable.__file__).



If your local installation was done correctly, then you should also make sure that 1) the location where you installed it is in your PYTHONPATH, 2) that if it is, the path is placed before that of the standard paths (lookup is sequential).
An easy way to check that it is in the path if you don't know where to look is just to uninstall the version installed through pip.



EDIT



Based on the edit to the question, yes, the version is still the same (see here)






share|improve this answer




















  • I am going to update the version to 0.6.5 in my local git clone
    – javadba
    Nov 10 at 20:27











  • $ipython -c "import datatable; print(datatable.__version__)" 0.6.5
    – javadba
    Nov 10 at 20:31













up vote
1
down vote



accepted







up vote
1
down vote



accepted






To look precisely at the module being used, the best way, as mentioned by @duhaime is to use import datatable; print(datatable.__file__).



If your local installation was done correctly, then you should also make sure that 1) the location where you installed it is in your PYTHONPATH, 2) that if it is, the path is placed before that of the standard paths (lookup is sequential).
An easy way to check that it is in the path if you don't know where to look is just to uninstall the version installed through pip.



EDIT



Based on the edit to the question, yes, the version is still the same (see here)






share|improve this answer












To look precisely at the module being used, the best way, as mentioned by @duhaime is to use import datatable; print(datatable.__file__).



If your local installation was done correctly, then you should also make sure that 1) the location where you installed it is in your PYTHONPATH, 2) that if it is, the path is placed before that of the standard paths (lookup is sequential).
An easy way to check that it is in the path if you don't know where to look is just to uninstall the version installed through pip.



EDIT



Based on the edit to the question, yes, the version is still the same (see here)







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 10 at 20:21









Silmathoron

7171619




7171619











  • I am going to update the version to 0.6.5 in my local git clone
    – javadba
    Nov 10 at 20:27











  • $ipython -c "import datatable; print(datatable.__version__)" 0.6.5
    – javadba
    Nov 10 at 20:31

















  • I am going to update the version to 0.6.5 in my local git clone
    – javadba
    Nov 10 at 20:27











  • $ipython -c "import datatable; print(datatable.__version__)" 0.6.5
    – javadba
    Nov 10 at 20:31
















I am going to update the version to 0.6.5 in my local git clone
– javadba
Nov 10 at 20:27





I am going to update the version to 0.6.5 in my local git clone
– javadba
Nov 10 at 20:27













$ipython -c "import datatable; print(datatable.__version__)" 0.6.5
– javadba
Nov 10 at 20:31





$ipython -c "import datatable; print(datatable.__version__)" 0.6.5
– javadba
Nov 10 at 20:31


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242959%2fhow-to-verify-a-locally-installed-version-of-a-module-is-the-one-used-by-pip%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

27

Image
www.msyz777.com_www.msyz888.com_www.msyz999.com window._bd_share_config="common":"bdSnsKey":,"bdText":"","bdMini":"2","bdMiniList":false,"bdPic":"","bdStyle":"1","bdSize":"16","share":,"image":"viewList":["qzone","tsina","tqq","renren","t163"],"viewText":"��������","viewSize":"16","selectShare":"bdContainerClass":null,"bdSelectMiniList":["qzone","tsina","tqq","renren","t163"];with(document)0[(getElementsByTagName('head')[0]||body).appendChild(createElement('script')).src='http://bdimg.share.baidu.com/static/...
Read more

Top Tejano songwriter Luis Silva dead of heart attack at 64

Image
Ramiro Burr's New Blog - to go back: www.ramiroburr.com From Latin rock to reggaeton, boleros to blues,Tex-Mex to Tejano, conjunto to corridos and beyond, Ramiro Burr has it covered. If you have a new CD release, a trivia question or are looking for tour info, post a message here or e-mail Ramiro directly at: musicreporter@gmail.com Top Tejano songwriter Luis Silva dead of heart attack at 64 By Ramiro Burr on October 23, 2008 8:40 AM | Permalink | Comments (12) | TrackBacks (0) UPDATE: Luis Silva Funeral Service details released Visitation 4-9 p.m. Saturday, Rosary service 6 p.m. Saturday at Porter Loring, 1101 McCullough Ave Funeral Service 10:30 a.m. Monday St. Anthony De Padua Catholic Church, Burial Service at Chapel Hills, 7735 Gibbs Sprawl Road. Porter Loring (210) 227-8221 Related New Flash: Irma Laura Lopez: long time record promoter killed in accident NewsFlash: 9:02 a.m. (New comments below) Luis Silva , one of the most well-known ...
Read more

Category:Rhetoric

Image
Help Category:Rhetoric From Wikipedia, the free encyclopedia Jump to navigation Jump to search Library cataloging and classification main topic rhetoric Library of Congress P301 Universal Decimal 808 Wikimedia Commons has media related to Rhetoric . The main article for this category is Rhetoric . Rhetorical terms, i.e. terms used to describe or analyze rhetorical arguments, including those in persuasive speeches and opinion editorials. Contents Top 0–9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Subcategories This category has the following 17 subcategories, out of 17 total. A ► Analogy‎ (2 C, 23 P) ► Apologetics‎ (5 C, 12 P) D ► Dialectic‎ (2 C, 21 P) ► Dialogues‎ (2 C, 38 P) F ► Fiction-writing mode‎ (4 C, 11 P) H ► Homiletics‎ (21 P) ► Hypocrisy‎ (11 P) P ► Populism‎ (13 C, 49 P) R ► Rhetoric theorists‎ (3 C,...
Read more