Unexpected behavior after running python setup.py install inside virtualenv












0















Here's my directory structure for reference.



|- package1
| '- abc.py
|- setup.py
|- examples
| '- directory1
| '- run.py
|- venv


After running python setup.py install, I see that a package1.egg file is placed successfully in venv/lib/python*/site-packages. When I run pip list the output contains the package1 entry with the correct version as described in the setup.py file.



Now, when I try to run python examples/directory1/run.py the first line of which is import package1, I get an error ModuleNotFoundError: No module named 'package1'. I get the same error when I launch the python interpreter and try to import package1 too.



What could I be doing wrong?










share|improve this question


















  • 2





    What does your setup.py look like? You also need __init__.pys in each package directory.

    – Matt Messersmith
    Nov 21 '18 at 19:30






  • 1





    Gah! That was the reason. I did not have an __init__.py in my package directory. Thank you for your suggestion. :)

    – cyberbeast
    Nov 21 '18 at 19:33
















0















Here's my directory structure for reference.



|- package1
| '- abc.py
|- setup.py
|- examples
| '- directory1
| '- run.py
|- venv


After running python setup.py install, I see that a package1.egg file is placed successfully in venv/lib/python*/site-packages. When I run pip list the output contains the package1 entry with the correct version as described in the setup.py file.



Now, when I try to run python examples/directory1/run.py the first line of which is import package1, I get an error ModuleNotFoundError: No module named 'package1'. I get the same error when I launch the python interpreter and try to import package1 too.



What could I be doing wrong?










share|improve this question


















  • 2





    What does your setup.py look like? You also need __init__.pys in each package directory.

    – Matt Messersmith
    Nov 21 '18 at 19:30






  • 1





    Gah! That was the reason. I did not have an __init__.py in my package directory. Thank you for your suggestion. :)

    – cyberbeast
    Nov 21 '18 at 19:33














0












0








0








Here's my directory structure for reference.



|- package1
| '- abc.py
|- setup.py
|- examples
| '- directory1
| '- run.py
|- venv


After running python setup.py install, I see that a package1.egg file is placed successfully in venv/lib/python*/site-packages. When I run pip list the output contains the package1 entry with the correct version as described in the setup.py file.



Now, when I try to run python examples/directory1/run.py the first line of which is import package1, I get an error ModuleNotFoundError: No module named 'package1'. I get the same error when I launch the python interpreter and try to import package1 too.



What could I be doing wrong?










share|improve this question














Here's my directory structure for reference.



|- package1
| '- abc.py
|- setup.py
|- examples
| '- directory1
| '- run.py
|- venv


After running python setup.py install, I see that a package1.egg file is placed successfully in venv/lib/python*/site-packages. When I run pip list the output contains the package1 entry with the correct version as described in the setup.py file.



Now, when I try to run python examples/directory1/run.py the first line of which is import package1, I get an error ModuleNotFoundError: No module named 'package1'. I get the same error when I launch the python interpreter and try to import package1 too.



What could I be doing wrong?







python python-3.x setup.py






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 19:17









cyberbeastcyberbeast

17014




17014








  • 2





    What does your setup.py look like? You also need __init__.pys in each package directory.

    – Matt Messersmith
    Nov 21 '18 at 19:30






  • 1





    Gah! That was the reason. I did not have an __init__.py in my package directory. Thank you for your suggestion. :)

    – cyberbeast
    Nov 21 '18 at 19:33














  • 2





    What does your setup.py look like? You also need __init__.pys in each package directory.

    – Matt Messersmith
    Nov 21 '18 at 19:30






  • 1





    Gah! That was the reason. I did not have an __init__.py in my package directory. Thank you for your suggestion. :)

    – cyberbeast
    Nov 21 '18 at 19:33








2




2





What does your setup.py look like? You also need __init__.pys in each package directory.

– Matt Messersmith
Nov 21 '18 at 19:30





What does your setup.py look like? You also need __init__.pys in each package directory.

– Matt Messersmith
Nov 21 '18 at 19:30




1




1





Gah! That was the reason. I did not have an __init__.py in my package directory. Thank you for your suggestion. :)

– cyberbeast
Nov 21 '18 at 19:33





Gah! That was the reason. I did not have an __init__.py in my package directory. Thank you for your suggestion. :)

– cyberbeast
Nov 21 '18 at 19:33












1 Answer
1






active

oldest

votes


















0














The answer is - Create a black file called __init__.py in the package directory structure.






share|improve this answer
























    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',
    autoActivateHeartbeat: false,
    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%2f53419110%2funexpected-behavior-after-running-python-setup-py-install-inside-virtualenv%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









    0














    The answer is - Create a black file called __init__.py in the package directory structure.






    share|improve this answer




























      0














      The answer is - Create a black file called __init__.py in the package directory structure.






      share|improve this answer


























        0












        0








        0







        The answer is - Create a black file called __init__.py in the package directory structure.






        share|improve this answer













        The answer is - Create a black file called __init__.py in the package directory structure.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 19:34









        cyberbeastcyberbeast

        17014




        17014
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419110%2funexpected-behavior-after-running-python-setup-py-install-inside-virtualenv%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

            Guess what letter conforming each word

            Port of Spain

            Run scheduled task as local user group (not BUILTIN)