Pylinter in Sublime text 3.1.1 still doesn't use Python2.7












10















Here are my pylinter settings:



{
// When versbose is 'true', various messages will be written to the console.
// values: true or false
"verbose": false,
// The full path to the Python executable you want to
// run Pylint with or simply use 'python'.
"python_bin": "/usr/bin/python2.7",
// The following paths will be added Pylint's Python path
"python_path": ,
// Optionally set the working directory
"working_dir": null,
// Full path to the lint.py module in the pylint package
"pylint_path": null,
// Optional full path to a Pylint configuration file
"pylint_rc": null,
// Set to true to automtically run Pylint on save
"run_on_save": true,
// Set to true to use graphical error icons
"use_icons": false,
"disable_outline": false,
// Status messages stay as long as cursor is on an error line
"message_stay": false,
// Ignore Pylint error types. Possible values:
// "R" : Refactor for a "good practice" metric violation
// "C" : Convention for coding standard violation
// "W" : Warning for stylistic problems, or minor programming issues
// "E" : Error for important programming issues (i.e. most probably bug)
// "F" : Fatal for errors which prevented further processing
"ignore": ,
// a list of strings of individual errors to disable, ex: ["C0301"]
"disable": ,
"plugins":
}


I've clearly put the python2.7 executable in the right place (I think). This is the path given to me by which python2.7.
And yet, a statement like print "test" still returns E0001 Missing parentheses in call to print - a classic python3 vs 2 error.



How can I get it to check for python2.7 errors?










share|improve this question























  • This is an interesting question indeed. From looking at the plugin code, if pylint is available on your path, then python_bin does exactly nothing at all (you can set it to nonsense for example and still lint just fine). I have found a lot of anecdotal evidence that they're planning on dropping Python 2 support, but I don't know if that means running it via Python 2 or checking Python 2 code.

    – OdatNurd
    Dec 6 '18 at 22:03






  • 1





    I found something for python2.7: stackoverflow.com/questions/51746255/… But yes, it looks like they will stop supporting Python 2 at the beginning of the year.

    – Xion
    Dec 12 '18 at 23:30
















10















Here are my pylinter settings:



{
// When versbose is 'true', various messages will be written to the console.
// values: true or false
"verbose": false,
// The full path to the Python executable you want to
// run Pylint with or simply use 'python'.
"python_bin": "/usr/bin/python2.7",
// The following paths will be added Pylint's Python path
"python_path": ,
// Optionally set the working directory
"working_dir": null,
// Full path to the lint.py module in the pylint package
"pylint_path": null,
// Optional full path to a Pylint configuration file
"pylint_rc": null,
// Set to true to automtically run Pylint on save
"run_on_save": true,
// Set to true to use graphical error icons
"use_icons": false,
"disable_outline": false,
// Status messages stay as long as cursor is on an error line
"message_stay": false,
// Ignore Pylint error types. Possible values:
// "R" : Refactor for a "good practice" metric violation
// "C" : Convention for coding standard violation
// "W" : Warning for stylistic problems, or minor programming issues
// "E" : Error for important programming issues (i.e. most probably bug)
// "F" : Fatal for errors which prevented further processing
"ignore": ,
// a list of strings of individual errors to disable, ex: ["C0301"]
"disable": ,
"plugins":
}


I've clearly put the python2.7 executable in the right place (I think). This is the path given to me by which python2.7.
And yet, a statement like print "test" still returns E0001 Missing parentheses in call to print - a classic python3 vs 2 error.



How can I get it to check for python2.7 errors?










share|improve this question























  • This is an interesting question indeed. From looking at the plugin code, if pylint is available on your path, then python_bin does exactly nothing at all (you can set it to nonsense for example and still lint just fine). I have found a lot of anecdotal evidence that they're planning on dropping Python 2 support, but I don't know if that means running it via Python 2 or checking Python 2 code.

    – OdatNurd
    Dec 6 '18 at 22:03






  • 1





    I found something for python2.7: stackoverflow.com/questions/51746255/… But yes, it looks like they will stop supporting Python 2 at the beginning of the year.

    – Xion
    Dec 12 '18 at 23:30














10












10








10








Here are my pylinter settings:



{
// When versbose is 'true', various messages will be written to the console.
// values: true or false
"verbose": false,
// The full path to the Python executable you want to
// run Pylint with or simply use 'python'.
"python_bin": "/usr/bin/python2.7",
// The following paths will be added Pylint's Python path
"python_path": ,
// Optionally set the working directory
"working_dir": null,
// Full path to the lint.py module in the pylint package
"pylint_path": null,
// Optional full path to a Pylint configuration file
"pylint_rc": null,
// Set to true to automtically run Pylint on save
"run_on_save": true,
// Set to true to use graphical error icons
"use_icons": false,
"disable_outline": false,
// Status messages stay as long as cursor is on an error line
"message_stay": false,
// Ignore Pylint error types. Possible values:
// "R" : Refactor for a "good practice" metric violation
// "C" : Convention for coding standard violation
// "W" : Warning for stylistic problems, or minor programming issues
// "E" : Error for important programming issues (i.e. most probably bug)
// "F" : Fatal for errors which prevented further processing
"ignore": ,
// a list of strings of individual errors to disable, ex: ["C0301"]
"disable": ,
"plugins":
}


I've clearly put the python2.7 executable in the right place (I think). This is the path given to me by which python2.7.
And yet, a statement like print "test" still returns E0001 Missing parentheses in call to print - a classic python3 vs 2 error.



How can I get it to check for python2.7 errors?










share|improve this question














Here are my pylinter settings:



{
// When versbose is 'true', various messages will be written to the console.
// values: true or false
"verbose": false,
// The full path to the Python executable you want to
// run Pylint with or simply use 'python'.
"python_bin": "/usr/bin/python2.7",
// The following paths will be added Pylint's Python path
"python_path": ,
// Optionally set the working directory
"working_dir": null,
// Full path to the lint.py module in the pylint package
"pylint_path": null,
// Optional full path to a Pylint configuration file
"pylint_rc": null,
// Set to true to automtically run Pylint on save
"run_on_save": true,
// Set to true to use graphical error icons
"use_icons": false,
"disable_outline": false,
// Status messages stay as long as cursor is on an error line
"message_stay": false,
// Ignore Pylint error types. Possible values:
// "R" : Refactor for a "good practice" metric violation
// "C" : Convention for coding standard violation
// "W" : Warning for stylistic problems, or minor programming issues
// "E" : Error for important programming issues (i.e. most probably bug)
// "F" : Fatal for errors which prevented further processing
"ignore": ,
// a list of strings of individual errors to disable, ex: ["C0301"]
"disable": ,
"plugins":
}


I've clearly put the python2.7 executable in the right place (I think). This is the path given to me by which python2.7.
And yet, a statement like print "test" still returns E0001 Missing parentheses in call to print - a classic python3 vs 2 error.



How can I get it to check for python2.7 errors?







python sublimetext3 pylint






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 15:26









LittleBobbyTablesLittleBobbyTables

1,50652249




1,50652249













  • This is an interesting question indeed. From looking at the plugin code, if pylint is available on your path, then python_bin does exactly nothing at all (you can set it to nonsense for example and still lint just fine). I have found a lot of anecdotal evidence that they're planning on dropping Python 2 support, but I don't know if that means running it via Python 2 or checking Python 2 code.

    – OdatNurd
    Dec 6 '18 at 22:03






  • 1





    I found something for python2.7: stackoverflow.com/questions/51746255/… But yes, it looks like they will stop supporting Python 2 at the beginning of the year.

    – Xion
    Dec 12 '18 at 23:30



















  • This is an interesting question indeed. From looking at the plugin code, if pylint is available on your path, then python_bin does exactly nothing at all (you can set it to nonsense for example and still lint just fine). I have found a lot of anecdotal evidence that they're planning on dropping Python 2 support, but I don't know if that means running it via Python 2 or checking Python 2 code.

    – OdatNurd
    Dec 6 '18 at 22:03






  • 1





    I found something for python2.7: stackoverflow.com/questions/51746255/… But yes, it looks like they will stop supporting Python 2 at the beginning of the year.

    – Xion
    Dec 12 '18 at 23:30

















This is an interesting question indeed. From looking at the plugin code, if pylint is available on your path, then python_bin does exactly nothing at all (you can set it to nonsense for example and still lint just fine). I have found a lot of anecdotal evidence that they're planning on dropping Python 2 support, but I don't know if that means running it via Python 2 or checking Python 2 code.

– OdatNurd
Dec 6 '18 at 22:03





This is an interesting question indeed. From looking at the plugin code, if pylint is available on your path, then python_bin does exactly nothing at all (you can set it to nonsense for example and still lint just fine). I have found a lot of anecdotal evidence that they're planning on dropping Python 2 support, but I don't know if that means running it via Python 2 or checking Python 2 code.

– OdatNurd
Dec 6 '18 at 22:03




1




1





I found something for python2.7: stackoverflow.com/questions/51746255/… But yes, it looks like they will stop supporting Python 2 at the beginning of the year.

– Xion
Dec 12 '18 at 23:30





I found something for python2.7: stackoverflow.com/questions/51746255/… But yes, it looks like they will stop supporting Python 2 at the beginning of the year.

– Xion
Dec 12 '18 at 23:30












1 Answer
1






active

oldest

votes


















0














Have you tried to set up "executable" as suggested in documentation?
http://www.sublimelinter.com/en/stable/linter_settings.html#executable



The snippet from my configuration (Windows):



"executable": "C:\Python27\Scripts\pylint.exe"





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%2f53415317%2fpylinter-in-sublime-text-3-1-1-still-doesnt-use-python2-7%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














    Have you tried to set up "executable" as suggested in documentation?
    http://www.sublimelinter.com/en/stable/linter_settings.html#executable



    The snippet from my configuration (Windows):



    "executable": "C:\Python27\Scripts\pylint.exe"





    share|improve this answer




























      0














      Have you tried to set up "executable" as suggested in documentation?
      http://www.sublimelinter.com/en/stable/linter_settings.html#executable



      The snippet from my configuration (Windows):



      "executable": "C:\Python27\Scripts\pylint.exe"





      share|improve this answer


























        0












        0








        0







        Have you tried to set up "executable" as suggested in documentation?
        http://www.sublimelinter.com/en/stable/linter_settings.html#executable



        The snippet from my configuration (Windows):



        "executable": "C:\Python27\Scripts\pylint.exe"





        share|improve this answer













        Have you tried to set up "executable" as suggested in documentation?
        http://www.sublimelinter.com/en/stable/linter_settings.html#executable



        The snippet from my configuration (Windows):



        "executable": "C:\Python27\Scripts\pylint.exe"






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 29 at 20:43









        gbajsongbajson

        505412




        505412
































            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%2f53415317%2fpylinter-in-sublime-text-3-1-1-still-doesnt-use-python2-7%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







            這個網誌中的熱門文章

            Hercules Kyvelos

            Tangent Lines Diagram Along Smooth Curve

            Yusuf al-Mu'taman ibn Hud