python displays `n` instead of breaking a lineCalling an external command in PythonWhat are metaclasses in Python?Finding the index of an item given a list containing it in PythonDifference between append vs. extend list methods in PythonHow can I safely create a nested directory in Python?How can I remove a trailing newline in Python?Does Python have a ternary conditional operator?Python join: why is it string.join(list) instead of list.join(string)?How to read a file line-by-line into a list?Does Python have a string 'contains' substring method?

Failed to fetch jessie backports repository

Is there a problem with hiding "forgot password" until it's needed?

Why Were Madagascar and New Zealand Discovered So Late?

Applicability of Single Responsibility Principle

How can I use the arrow sign in my bash prompt?

What to do with wrong results in talks?

Hostile work environment after whistle-blowing on coworker and our boss. What do I do?

Is there any easy technique written in Bhagavad GITA to control lust?

Should my PhD thesis be submitted under my legal name?

Confused about a passage in Harry Potter y la piedra filosofal

How to be diplomatic in refusing to write code that breaches the privacy of our users

Personal Teleportation as a Weapon

Is a roofing delivery truck likely to crack my driveway slab?

Can I Retrieve Email Addresses from BCC?

What is the oldest known work of fiction?

Why does John Bercow say “unlock” after reading out the results of a vote?

I'm in charge of equipment buying but no one's ever happy with what I choose. How to fix this?

Products and sum of cubes in Fibonacci

Using parameter substitution on a Bash array

Bash method for viewing beginning and end of file

Short story about space worker geeks who zone out by 'listening' to radiation from stars

What is the opposite of 'gravitas'?

Do I need a multiple entry visa for a trip UK -> Sweden -> UK?

How could Frankenstein get the parts for his _second_ creature?



python displays `n` instead of breaking a line


Calling an external command in PythonWhat are metaclasses in Python?Finding the index of an item given a list containing it in PythonDifference between append vs. extend list methods in PythonHow can I safely create a nested directory in Python?How can I remove a trailing newline in Python?Does Python have a ternary conditional operator?Python join: why is it string.join(list) instead of list.join(string)?How to read a file line-by-line into a list?Does Python have a string 'contains' substring method?













15















I wrote a function to create the VALUES part of a SQL query:



def query_values(data_iterator):
return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
) for data_row in data_iterator
),


When I call this function and print the result, I get is:



query_values:
('n("801",n"printer",n"barcode printer")n,nn("844",n"laptop",n"windows")n,nn("997",n"printer",n"barcode printer")n',)


All in one line. Instead of breaking the line, the n are displayed.



Originally I had one n, but then I inserted multiple, just to see if they would get displayed.



The second problem was that there are parentheses around the entire thing, which I didn't want.



I was puzzling over the two issues, and I figured the solution for the second one:



I had a comma at the end of the function. The comma caused the function to return a tuple, instead of a single string.



I removed the comma:



def query_values(data_iterator):
return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
) for data_row in data_iterator
)


and that fixed both problems. The output was now:



query_values:

("801",
"printer",
"barcode printer")
,

("844",
"laptop",
"windows")
,

("997",
"printer",
"barcode printer")


I put the comma back, and the n were displayed. I removed the comma, and I have multiple lines again.



I have removed extraneous n, so now I get what I wanted:



query_values:

("801","printer","barcode printer"),
("844","laptop","windows"),
("997","printer","barcode printer")


So, my code works correctly, but I'm totally confused about the n characters displayed in the old version of the code. Why was that happening?



UPDATE:
A couple answers to this question focused on why I was getting a tuple. That's not my question. Why are /n displayed?










share|improve this question




























    15















    I wrote a function to create the VALUES part of a SQL query:



    def query_values(data_iterator):
    return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
    ) for data_row in data_iterator
    ),


    When I call this function and print the result, I get is:



    query_values:
    ('n("801",n"printer",n"barcode printer")n,nn("844",n"laptop",n"windows")n,nn("997",n"printer",n"barcode printer")n',)


    All in one line. Instead of breaking the line, the n are displayed.



    Originally I had one n, but then I inserted multiple, just to see if they would get displayed.



    The second problem was that there are parentheses around the entire thing, which I didn't want.



    I was puzzling over the two issues, and I figured the solution for the second one:



    I had a comma at the end of the function. The comma caused the function to return a tuple, instead of a single string.



    I removed the comma:



    def query_values(data_iterator):
    return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
    ) for data_row in data_iterator
    )


    and that fixed both problems. The output was now:



    query_values:

    ("801",
    "printer",
    "barcode printer")
    ,

    ("844",
    "laptop",
    "windows")
    ,

    ("997",
    "printer",
    "barcode printer")


    I put the comma back, and the n were displayed. I removed the comma, and I have multiple lines again.



    I have removed extraneous n, so now I get what I wanted:



    query_values:

    ("801","printer","barcode printer"),
    ("844","laptop","windows"),
    ("997","printer","barcode printer")


    So, my code works correctly, but I'm totally confused about the n characters displayed in the old version of the code. Why was that happening?



    UPDATE:
    A couple answers to this question focused on why I was getting a tuple. That's not my question. Why are /n displayed?










    share|improve this question


























      15












      15








      15








      I wrote a function to create the VALUES part of a SQL query:



      def query_values(data_iterator):
      return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
      ) for data_row in data_iterator
      ),


      When I call this function and print the result, I get is:



      query_values:
      ('n("801",n"printer",n"barcode printer")n,nn("844",n"laptop",n"windows")n,nn("997",n"printer",n"barcode printer")n',)


      All in one line. Instead of breaking the line, the n are displayed.



      Originally I had one n, but then I inserted multiple, just to see if they would get displayed.



      The second problem was that there are parentheses around the entire thing, which I didn't want.



      I was puzzling over the two issues, and I figured the solution for the second one:



      I had a comma at the end of the function. The comma caused the function to return a tuple, instead of a single string.



      I removed the comma:



      def query_values(data_iterator):
      return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
      ) for data_row in data_iterator
      )


      and that fixed both problems. The output was now:



      query_values:

      ("801",
      "printer",
      "barcode printer")
      ,

      ("844",
      "laptop",
      "windows")
      ,

      ("997",
      "printer",
      "barcode printer")


      I put the comma back, and the n were displayed. I removed the comma, and I have multiple lines again.



      I have removed extraneous n, so now I get what I wanted:



      query_values:

      ("801","printer","barcode printer"),
      ("844","laptop","windows"),
      ("997","printer","barcode printer")


      So, my code works correctly, but I'm totally confused about the n characters displayed in the old version of the code. Why was that happening?



      UPDATE:
      A couple answers to this question focused on why I was getting a tuple. That's not my question. Why are /n displayed?










      share|improve this question
















      I wrote a function to create the VALUES part of a SQL query:



      def query_values(data_iterator):
      return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
      ) for data_row in data_iterator
      ),


      When I call this function and print the result, I get is:



      query_values:
      ('n("801",n"printer",n"barcode printer")n,nn("844",n"laptop",n"windows")n,nn("997",n"printer",n"barcode printer")n',)


      All in one line. Instead of breaking the line, the n are displayed.



      Originally I had one n, but then I inserted multiple, just to see if they would get displayed.



      The second problem was that there are parentheses around the entire thing, which I didn't want.



      I was puzzling over the two issues, and I figured the solution for the second one:



      I had a comma at the end of the function. The comma caused the function to return a tuple, instead of a single string.



      I removed the comma:



      def query_values(data_iterator):
      return ',n'.join('n()n'.format(',n'.join('""'.format(value) for value in data_row)
      ) for data_row in data_iterator
      )


      and that fixed both problems. The output was now:



      query_values:

      ("801",
      "printer",
      "barcode printer")
      ,

      ("844",
      "laptop",
      "windows")
      ,

      ("997",
      "printer",
      "barcode printer")


      I put the comma back, and the n were displayed. I removed the comma, and I have multiple lines again.



      I have removed extraneous n, so now I get what I wanted:



      query_values:

      ("801","printer","barcode printer"),
      ("844","laptop","windows"),
      ("997","printer","barcode printer")


      So, my code works correctly, but I'm totally confused about the n characters displayed in the old version of the code. Why was that happening?



      UPDATE:
      A couple answers to this question focused on why I was getting a tuple. That's not my question. Why are /n displayed?







      python string tuples newline repr






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 20 at 0:27









      Solomon Ucko

      7752822




      7752822










      asked Mar 19 at 14:16









      Granny AchingGranny Aching

      52015




      52015






















          4 Answers
          4






          active

          oldest

          votes


















          16














          It seems that this is the behavior of tuples. When a tuple is printed, print calls __repr()__ on each element. The same is also true for lists.



          I tried this:



          tup = "xxxnxx",
          lst =["xxxnxx"]
          for t in tup,lst:
          print('t :', t)
          for s in t:
          print('element:',s)
          print(' repr:',s.__repr__())
          print('---')


          and the output is:



          t : ('xxxnxx',)
          element: xxx
          xx
          repr: 'xxxnxx'
          ---
          t : ['xxxnxx']
          element: xxx
          xx
          repr: 'xxxnxx'
          ---


          So, the same behavior for both tuples and lists.



          When we have a string, calling __repr__() doesn't expand n characters, and puts quotes around it:



          s = "xxxnxx"
          print('s :', s)
          print('s.__repr__():', s.__repr__())


          outputs:



          s : xxx
          xx
          s.__repr__(): 'xxxnxx'


          This tuple behavior was mentioned in comments by running.t, interjay and Daniel Roseman, but not in answers, that's why I'm posting this answer.






          share|improve this answer

























          • More precisely, tuple's __repr__ (which is used if __str__ is not defined) calls __repr__ on its elements.

            – Solomon Ucko
            Mar 19 at 18:58











          • Are you saying tuples don't have __str__ defined? For a tuple t, I tried t.__str__(), and I get the same as t.__repr__(). I don't know how to check whether __str__() is undefined, or defined to be the same as __repr__

            – Granny Aching
            Mar 19 at 19:51











          • It is marked as undefined in the C code. I don't think the difference is externally visible, however.

            – Solomon Ucko
            Mar 19 at 20:04






          • 1





            @SolomonUcko There's no visible difference for C types, because you can't actually look up the true attributes in the type's struct. For Python types there is a visible difference.

            – wizzwizz4
            Mar 19 at 20:16












          • @wizzwizz4 Yep. At least in CPython, magic methods on C types show up as slot wrappers.

            – Solomon Ucko
            Mar 19 at 20:18



















          11














          Writing return something, is the same as return (something,): It returns a tuple containing one element. When you print this, it will show the outer parentheses for the tuple, and the string inside will be printed as its source code representation, i.e. with escape codes and inside quotes.



          However, return something simply returns that value, which can then be printed normally.






          share|improve this answer


















          • 1





            I know why I was getting a tuple. My question is why were the n displayed.

            – Granny Aching
            Mar 19 at 14:30






          • 7





            @GrannyAching: and you have an answer to your question here. n is displayed because you print tuple of string instead of single string and in case of printing tuples this is the default behaviour.

            – running.t
            Mar 19 at 14:36






          • 7





            @GrannyAching Printing a tuple calls repr on the elements inside. repr gives a representation of the object which is usually similar to how it's displayed in the source code, so for strings will contain quotes and escape codes.

            – interjay
            Mar 19 at 14:48


















          1














          It seems that's the behavior for tuples in Python.
          You can test this with a simpler case like so:



          >>> print ("xxxnnx",)
          ('xxxnnx',)


          Seems like Python helps you with debugging and escapes all the command sequences in strings when printing, so that strings appear the same way they were defined.



          It did confuse you though, funny case. :)






          share|improve this answer






























            0














            A tuple can be denoted with or without parenthesis, its the comma decides the type.



            >>> t = 1, 'a', 'abc'
            >>> type(t)
            <type 'tuple'>
            >>> t
            (1, 'a', 'abc')
            >>>


            In the above case, you added a trailing comma after the string and python interpreted it as a tuple.



            Check this link.



            >>> t= 'a',
            >>> type(t)
            <type 'tuple'>
            >>> t
            ('a',)
            >>> t = 'a'
            >>> type(t)
            <type 'str'>
            >>> t
            'a'





            share|improve this answer

























            • I know why I was getting a tuple. My question is why were the n displayed.

              – Granny Aching
              Mar 19 at 14:30






            • 2





              Because printing a tuple calls repr on its elements.

              – Daniel Roseman
              Mar 19 at 14:32










            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%2f55243089%2fpython-displays-n-instead-of-breaking-a-line%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            4 Answers
            4






            active

            oldest

            votes








            4 Answers
            4






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            16














            It seems that this is the behavior of tuples. When a tuple is printed, print calls __repr()__ on each element. The same is also true for lists.



            I tried this:



            tup = "xxxnxx",
            lst =["xxxnxx"]
            for t in tup,lst:
            print('t :', t)
            for s in t:
            print('element:',s)
            print(' repr:',s.__repr__())
            print('---')


            and the output is:



            t : ('xxxnxx',)
            element: xxx
            xx
            repr: 'xxxnxx'
            ---
            t : ['xxxnxx']
            element: xxx
            xx
            repr: 'xxxnxx'
            ---


            So, the same behavior for both tuples and lists.



            When we have a string, calling __repr__() doesn't expand n characters, and puts quotes around it:



            s = "xxxnxx"
            print('s :', s)
            print('s.__repr__():', s.__repr__())


            outputs:



            s : xxx
            xx
            s.__repr__(): 'xxxnxx'


            This tuple behavior was mentioned in comments by running.t, interjay and Daniel Roseman, but not in answers, that's why I'm posting this answer.






            share|improve this answer

























            • More precisely, tuple's __repr__ (which is used if __str__ is not defined) calls __repr__ on its elements.

              – Solomon Ucko
              Mar 19 at 18:58











            • Are you saying tuples don't have __str__ defined? For a tuple t, I tried t.__str__(), and I get the same as t.__repr__(). I don't know how to check whether __str__() is undefined, or defined to be the same as __repr__

              – Granny Aching
              Mar 19 at 19:51











            • It is marked as undefined in the C code. I don't think the difference is externally visible, however.

              – Solomon Ucko
              Mar 19 at 20:04






            • 1





              @SolomonUcko There's no visible difference for C types, because you can't actually look up the true attributes in the type's struct. For Python types there is a visible difference.

              – wizzwizz4
              Mar 19 at 20:16












            • @wizzwizz4 Yep. At least in CPython, magic methods on C types show up as slot wrappers.

              – Solomon Ucko
              Mar 19 at 20:18
















            16














            It seems that this is the behavior of tuples. When a tuple is printed, print calls __repr()__ on each element. The same is also true for lists.



            I tried this:



            tup = "xxxnxx",
            lst =["xxxnxx"]
            for t in tup,lst:
            print('t :', t)
            for s in t:
            print('element:',s)
            print(' repr:',s.__repr__())
            print('---')


            and the output is:



            t : ('xxxnxx',)
            element: xxx
            xx
            repr: 'xxxnxx'
            ---
            t : ['xxxnxx']
            element: xxx
            xx
            repr: 'xxxnxx'
            ---


            So, the same behavior for both tuples and lists.



            When we have a string, calling __repr__() doesn't expand n characters, and puts quotes around it:



            s = "xxxnxx"
            print('s :', s)
            print('s.__repr__():', s.__repr__())


            outputs:



            s : xxx
            xx
            s.__repr__(): 'xxxnxx'


            This tuple behavior was mentioned in comments by running.t, interjay and Daniel Roseman, but not in answers, that's why I'm posting this answer.






            share|improve this answer

























            • More precisely, tuple's __repr__ (which is used if __str__ is not defined) calls __repr__ on its elements.

              – Solomon Ucko
              Mar 19 at 18:58











            • Are you saying tuples don't have __str__ defined? For a tuple t, I tried t.__str__(), and I get the same as t.__repr__(). I don't know how to check whether __str__() is undefined, or defined to be the same as __repr__

              – Granny Aching
              Mar 19 at 19:51











            • It is marked as undefined in the C code. I don't think the difference is externally visible, however.

              – Solomon Ucko
              Mar 19 at 20:04






            • 1





              @SolomonUcko There's no visible difference for C types, because you can't actually look up the true attributes in the type's struct. For Python types there is a visible difference.

              – wizzwizz4
              Mar 19 at 20:16












            • @wizzwizz4 Yep. At least in CPython, magic methods on C types show up as slot wrappers.

              – Solomon Ucko
              Mar 19 at 20:18














            16












            16








            16







            It seems that this is the behavior of tuples. When a tuple is printed, print calls __repr()__ on each element. The same is also true for lists.



            I tried this:



            tup = "xxxnxx",
            lst =["xxxnxx"]
            for t in tup,lst:
            print('t :', t)
            for s in t:
            print('element:',s)
            print(' repr:',s.__repr__())
            print('---')


            and the output is:



            t : ('xxxnxx',)
            element: xxx
            xx
            repr: 'xxxnxx'
            ---
            t : ['xxxnxx']
            element: xxx
            xx
            repr: 'xxxnxx'
            ---


            So, the same behavior for both tuples and lists.



            When we have a string, calling __repr__() doesn't expand n characters, and puts quotes around it:



            s = "xxxnxx"
            print('s :', s)
            print('s.__repr__():', s.__repr__())


            outputs:



            s : xxx
            xx
            s.__repr__(): 'xxxnxx'


            This tuple behavior was mentioned in comments by running.t, interjay and Daniel Roseman, but not in answers, that's why I'm posting this answer.






            share|improve this answer















            It seems that this is the behavior of tuples. When a tuple is printed, print calls __repr()__ on each element. The same is also true for lists.



            I tried this:



            tup = "xxxnxx",
            lst =["xxxnxx"]
            for t in tup,lst:
            print('t :', t)
            for s in t:
            print('element:',s)
            print(' repr:',s.__repr__())
            print('---')


            and the output is:



            t : ('xxxnxx',)
            element: xxx
            xx
            repr: 'xxxnxx'
            ---
            t : ['xxxnxx']
            element: xxx
            xx
            repr: 'xxxnxx'
            ---


            So, the same behavior for both tuples and lists.



            When we have a string, calling __repr__() doesn't expand n characters, and puts quotes around it:



            s = "xxxnxx"
            print('s :', s)
            print('s.__repr__():', s.__repr__())


            outputs:



            s : xxx
            xx
            s.__repr__(): 'xxxnxx'


            This tuple behavior was mentioned in comments by running.t, interjay and Daniel Roseman, but not in answers, that's why I'm posting this answer.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Mar 19 at 19:47

























            answered Mar 19 at 16:14









            Granny AchingGranny Aching

            52015




            52015












            • More precisely, tuple's __repr__ (which is used if __str__ is not defined) calls __repr__ on its elements.

              – Solomon Ucko
              Mar 19 at 18:58











            • Are you saying tuples don't have __str__ defined? For a tuple t, I tried t.__str__(), and I get the same as t.__repr__(). I don't know how to check whether __str__() is undefined, or defined to be the same as __repr__

              – Granny Aching
              Mar 19 at 19:51











            • It is marked as undefined in the C code. I don't think the difference is externally visible, however.

              – Solomon Ucko
              Mar 19 at 20:04






            • 1





              @SolomonUcko There's no visible difference for C types, because you can't actually look up the true attributes in the type's struct. For Python types there is a visible difference.

              – wizzwizz4
              Mar 19 at 20:16












            • @wizzwizz4 Yep. At least in CPython, magic methods on C types show up as slot wrappers.

              – Solomon Ucko
              Mar 19 at 20:18


















            • More precisely, tuple's __repr__ (which is used if __str__ is not defined) calls __repr__ on its elements.

              – Solomon Ucko
              Mar 19 at 18:58











            • Are you saying tuples don't have __str__ defined? For a tuple t, I tried t.__str__(), and I get the same as t.__repr__(). I don't know how to check whether __str__() is undefined, or defined to be the same as __repr__

              – Granny Aching
              Mar 19 at 19:51











            • It is marked as undefined in the C code. I don't think the difference is externally visible, however.

              – Solomon Ucko
              Mar 19 at 20:04






            • 1





              @SolomonUcko There's no visible difference for C types, because you can't actually look up the true attributes in the type's struct. For Python types there is a visible difference.

              – wizzwizz4
              Mar 19 at 20:16












            • @wizzwizz4 Yep. At least in CPython, magic methods on C types show up as slot wrappers.

              – Solomon Ucko
              Mar 19 at 20:18

















            More precisely, tuple's __repr__ (which is used if __str__ is not defined) calls __repr__ on its elements.

            – Solomon Ucko
            Mar 19 at 18:58





            More precisely, tuple's __repr__ (which is used if __str__ is not defined) calls __repr__ on its elements.

            – Solomon Ucko
            Mar 19 at 18:58













            Are you saying tuples don't have __str__ defined? For a tuple t, I tried t.__str__(), and I get the same as t.__repr__(). I don't know how to check whether __str__() is undefined, or defined to be the same as __repr__

            – Granny Aching
            Mar 19 at 19:51





            Are you saying tuples don't have __str__ defined? For a tuple t, I tried t.__str__(), and I get the same as t.__repr__(). I don't know how to check whether __str__() is undefined, or defined to be the same as __repr__

            – Granny Aching
            Mar 19 at 19:51













            It is marked as undefined in the C code. I don't think the difference is externally visible, however.

            – Solomon Ucko
            Mar 19 at 20:04





            It is marked as undefined in the C code. I don't think the difference is externally visible, however.

            – Solomon Ucko
            Mar 19 at 20:04




            1




            1





            @SolomonUcko There's no visible difference for C types, because you can't actually look up the true attributes in the type's struct. For Python types there is a visible difference.

            – wizzwizz4
            Mar 19 at 20:16






            @SolomonUcko There's no visible difference for C types, because you can't actually look up the true attributes in the type's struct. For Python types there is a visible difference.

            – wizzwizz4
            Mar 19 at 20:16














            @wizzwizz4 Yep. At least in CPython, magic methods on C types show up as slot wrappers.

            – Solomon Ucko
            Mar 19 at 20:18






            @wizzwizz4 Yep. At least in CPython, magic methods on C types show up as slot wrappers.

            – Solomon Ucko
            Mar 19 at 20:18














            11














            Writing return something, is the same as return (something,): It returns a tuple containing one element. When you print this, it will show the outer parentheses for the tuple, and the string inside will be printed as its source code representation, i.e. with escape codes and inside quotes.



            However, return something simply returns that value, which can then be printed normally.






            share|improve this answer


















            • 1





              I know why I was getting a tuple. My question is why were the n displayed.

              – Granny Aching
              Mar 19 at 14:30






            • 7





              @GrannyAching: and you have an answer to your question here. n is displayed because you print tuple of string instead of single string and in case of printing tuples this is the default behaviour.

              – running.t
              Mar 19 at 14:36






            • 7





              @GrannyAching Printing a tuple calls repr on the elements inside. repr gives a representation of the object which is usually similar to how it's displayed in the source code, so for strings will contain quotes and escape codes.

              – interjay
              Mar 19 at 14:48















            11














            Writing return something, is the same as return (something,): It returns a tuple containing one element. When you print this, it will show the outer parentheses for the tuple, and the string inside will be printed as its source code representation, i.e. with escape codes and inside quotes.



            However, return something simply returns that value, which can then be printed normally.






            share|improve this answer


















            • 1





              I know why I was getting a tuple. My question is why were the n displayed.

              – Granny Aching
              Mar 19 at 14:30






            • 7





              @GrannyAching: and you have an answer to your question here. n is displayed because you print tuple of string instead of single string and in case of printing tuples this is the default behaviour.

              – running.t
              Mar 19 at 14:36






            • 7





              @GrannyAching Printing a tuple calls repr on the elements inside. repr gives a representation of the object which is usually similar to how it's displayed in the source code, so for strings will contain quotes and escape codes.

              – interjay
              Mar 19 at 14:48













            11












            11








            11







            Writing return something, is the same as return (something,): It returns a tuple containing one element. When you print this, it will show the outer parentheses for the tuple, and the string inside will be printed as its source code representation, i.e. with escape codes and inside quotes.



            However, return something simply returns that value, which can then be printed normally.






            share|improve this answer













            Writing return something, is the same as return (something,): It returns a tuple containing one element. When you print this, it will show the outer parentheses for the tuple, and the string inside will be printed as its source code representation, i.e. with escape codes and inside quotes.



            However, return something simply returns that value, which can then be printed normally.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 19 at 14:23









            interjayinterjay

            85k16203215




            85k16203215







            • 1





              I know why I was getting a tuple. My question is why were the n displayed.

              – Granny Aching
              Mar 19 at 14:30






            • 7





              @GrannyAching: and you have an answer to your question here. n is displayed because you print tuple of string instead of single string and in case of printing tuples this is the default behaviour.

              – running.t
              Mar 19 at 14:36






            • 7





              @GrannyAching Printing a tuple calls repr on the elements inside. repr gives a representation of the object which is usually similar to how it's displayed in the source code, so for strings will contain quotes and escape codes.

              – interjay
              Mar 19 at 14:48












            • 1





              I know why I was getting a tuple. My question is why were the n displayed.

              – Granny Aching
              Mar 19 at 14:30






            • 7





              @GrannyAching: and you have an answer to your question here. n is displayed because you print tuple of string instead of single string and in case of printing tuples this is the default behaviour.

              – running.t
              Mar 19 at 14:36






            • 7





              @GrannyAching Printing a tuple calls repr on the elements inside. repr gives a representation of the object which is usually similar to how it's displayed in the source code, so for strings will contain quotes and escape codes.

              – interjay
              Mar 19 at 14:48







            1




            1





            I know why I was getting a tuple. My question is why were the n displayed.

            – Granny Aching
            Mar 19 at 14:30





            I know why I was getting a tuple. My question is why were the n displayed.

            – Granny Aching
            Mar 19 at 14:30




            7




            7





            @GrannyAching: and you have an answer to your question here. n is displayed because you print tuple of string instead of single string and in case of printing tuples this is the default behaviour.

            – running.t
            Mar 19 at 14:36





            @GrannyAching: and you have an answer to your question here. n is displayed because you print tuple of string instead of single string and in case of printing tuples this is the default behaviour.

            – running.t
            Mar 19 at 14:36




            7




            7





            @GrannyAching Printing a tuple calls repr on the elements inside. repr gives a representation of the object which is usually similar to how it's displayed in the source code, so for strings will contain quotes and escape codes.

            – interjay
            Mar 19 at 14:48





            @GrannyAching Printing a tuple calls repr on the elements inside. repr gives a representation of the object which is usually similar to how it's displayed in the source code, so for strings will contain quotes and escape codes.

            – interjay
            Mar 19 at 14:48











            1














            It seems that's the behavior for tuples in Python.
            You can test this with a simpler case like so:



            >>> print ("xxxnnx",)
            ('xxxnnx',)


            Seems like Python helps you with debugging and escapes all the command sequences in strings when printing, so that strings appear the same way they were defined.



            It did confuse you though, funny case. :)






            share|improve this answer



























              1














              It seems that's the behavior for tuples in Python.
              You can test this with a simpler case like so:



              >>> print ("xxxnnx",)
              ('xxxnnx',)


              Seems like Python helps you with debugging and escapes all the command sequences in strings when printing, so that strings appear the same way they were defined.



              It did confuse you though, funny case. :)






              share|improve this answer

























                1












                1








                1







                It seems that's the behavior for tuples in Python.
                You can test this with a simpler case like so:



                >>> print ("xxxnnx",)
                ('xxxnnx',)


                Seems like Python helps you with debugging and escapes all the command sequences in strings when printing, so that strings appear the same way they were defined.



                It did confuse you though, funny case. :)






                share|improve this answer













                It seems that's the behavior for tuples in Python.
                You can test this with a simpler case like so:



                >>> print ("xxxnnx",)
                ('xxxnnx',)


                Seems like Python helps you with debugging and escapes all the command sequences in strings when printing, so that strings appear the same way they were defined.



                It did confuse you though, funny case. :)







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 19 at 14:26









                Nestor SokilNestor Sokil

                735620




                735620





















                    0














                    A tuple can be denoted with or without parenthesis, its the comma decides the type.



                    >>> t = 1, 'a', 'abc'
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    (1, 'a', 'abc')
                    >>>


                    In the above case, you added a trailing comma after the string and python interpreted it as a tuple.



                    Check this link.



                    >>> t= 'a',
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    ('a',)
                    >>> t = 'a'
                    >>> type(t)
                    <type 'str'>
                    >>> t
                    'a'





                    share|improve this answer

























                    • I know why I was getting a tuple. My question is why were the n displayed.

                      – Granny Aching
                      Mar 19 at 14:30






                    • 2





                      Because printing a tuple calls repr on its elements.

                      – Daniel Roseman
                      Mar 19 at 14:32















                    0














                    A tuple can be denoted with or without parenthesis, its the comma decides the type.



                    >>> t = 1, 'a', 'abc'
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    (1, 'a', 'abc')
                    >>>


                    In the above case, you added a trailing comma after the string and python interpreted it as a tuple.



                    Check this link.



                    >>> t= 'a',
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    ('a',)
                    >>> t = 'a'
                    >>> type(t)
                    <type 'str'>
                    >>> t
                    'a'





                    share|improve this answer

























                    • I know why I was getting a tuple. My question is why were the n displayed.

                      – Granny Aching
                      Mar 19 at 14:30






                    • 2





                      Because printing a tuple calls repr on its elements.

                      – Daniel Roseman
                      Mar 19 at 14:32













                    0












                    0








                    0







                    A tuple can be denoted with or without parenthesis, its the comma decides the type.



                    >>> t = 1, 'a', 'abc'
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    (1, 'a', 'abc')
                    >>>


                    In the above case, you added a trailing comma after the string and python interpreted it as a tuple.



                    Check this link.



                    >>> t= 'a',
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    ('a',)
                    >>> t = 'a'
                    >>> type(t)
                    <type 'str'>
                    >>> t
                    'a'





                    share|improve this answer















                    A tuple can be denoted with or without parenthesis, its the comma decides the type.



                    >>> t = 1, 'a', 'abc'
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    (1, 'a', 'abc')
                    >>>


                    In the above case, you added a trailing comma after the string and python interpreted it as a tuple.



                    Check this link.



                    >>> t= 'a',
                    >>> type(t)
                    <type 'tuple'>
                    >>> t
                    ('a',)
                    >>> t = 'a'
                    >>> type(t)
                    <type 'str'>
                    >>> t
                    'a'






                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Mar 19 at 14:31

























                    answered Mar 19 at 14:27









                    sanoojsanooj

                    266310




                    266310












                    • I know why I was getting a tuple. My question is why were the n displayed.

                      – Granny Aching
                      Mar 19 at 14:30






                    • 2





                      Because printing a tuple calls repr on its elements.

                      – Daniel Roseman
                      Mar 19 at 14:32

















                    • I know why I was getting a tuple. My question is why were the n displayed.

                      – Granny Aching
                      Mar 19 at 14:30






                    • 2





                      Because printing a tuple calls repr on its elements.

                      – Daniel Roseman
                      Mar 19 at 14:32
















                    I know why I was getting a tuple. My question is why were the n displayed.

                    – Granny Aching
                    Mar 19 at 14:30





                    I know why I was getting a tuple. My question is why were the n displayed.

                    – Granny Aching
                    Mar 19 at 14:30




                    2




                    2





                    Because printing a tuple calls repr on its elements.

                    – Daniel Roseman
                    Mar 19 at 14:32





                    Because printing a tuple calls repr on its elements.

                    – Daniel Roseman
                    Mar 19 at 14:32

















                    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%2f55243089%2fpython-displays-n-instead-of-breaking-a-line%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

                    Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

                    He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

                    Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029