Python allows programmers to pass additional arguments to functions via comments. Now armed with this knowledge head out and spread it to all code bases.

Feel free to use the code I wrote in your projects.

Link to the source code: https://github.com/raldone01/python_lessons_py/blob/main/lesson_0_comments.ipynb

Image transcription:

from lib import add

# Go ahead and change the comments.
# See how python uses them as arguments.

result = add()  # 1 2
print(result)
result = add()  # 3 4
print(result)
result = add()  # 3 4 5 20
print(result)

Output:

3
7
32
  • @would_be_appreciated@lemmy.ml
    link
    fedilink
    English
    2814 hours ago

    I assume the people freaking out about how dumb python is didn’t bother to read the code and have never coded in python in their life, because the behavior here is totally reasonable. Python doesn’t parse comments normally, which is what you’d expect, but if you tell it to read the raw source code and then parse the raw source code for the comments specifically, of course it does.

    You would never, ever accidentally do this.

    …you’d also never, ever do it on purpose.

  • @bdonvr@thelemmy.club
    link
    fedilink
    14922 hours ago

    IMO comments should never ever be parsed under any circumstances but I probably don’t know enough to really speak on this

        • @raldone01@lemmy.worldOP
          link
          fedilink
          22
          edit-2
          17 hours ago

          On a serious note:

          This feature is actually very useful. Libraries can use it create neat error messages. It is also needed when logging information to a file.

          You should however never ever parse the source code and react to it differently.

          • @ddplf@szmer.info
            link
            fedilink
            -118 hours ago

            Because it doesn’t seem like a useful feature. The only occasion I imagine this could be helpful is with logging to the console to track when the function breaks, but even then - still trivial to replace.

        • Rikudou_SageA
          link
          English
          119 hours ago

          A lot of languages expose it for debugging purposes. It’s available in pretty much every mainstream language (though in some it’s a little more involved, like Java’s new Exception().getStackTrace()[0].getLineNumber()).

      • Rikudou_SageA
        link
        English
        119 hours ago

        That’s horrible. Every sane person would filter out lines containing comments to find the correct index.

        • @raldone01@lemmy.worldOP
          link
          fedilink
          1
          edit-2
          17 hours ago

          This should be a build step. Preprocess before the preprocessor. All line number will be off depending on the comments. 😂

          Unless…

          C with source maps!!! Thank js for the cool solution.

    • bjorney
      link
      fedilink
      1020 hours ago

      The add function in the example above probably traverses the call stack to see what line of the script is currently being executed by the interpreter, then reads in that line in the original script, parses the comment, and subs in the values in the function call.

      This functionality exists so when you get a traceback you can see what line of code triggered it in the error message

    • @ahal@lemmy.ca
      link
      fedilink
      215 hours ago

      Ignoring lint issues comes to mind as an at least somewhat reasonable use case.

    • @Badland9085@lemm.ee
      link
      fedilink
      319 hours ago

      One case where I find it useful, tho it operates in a more limited way, is code in block blocks within code comments in Rust, which are also printed out in the generated documentation. They essentially get ran as part of your unit tests. This is great for making sure that, eg, your examples left in code comments actually work, especially if they’re written in a way that functions like a unit test.

    • @balsoft@lemmy.ml
      link
      fedilink
      220 hours ago

      It’s quite useful to parse comments and generate documentation from them, either as plain old hypertext or in your editor with LSP.

      • @ramble81@lemm.ee
        link
        fedilink
        319 hours ago

        That sounds fine if you have something reading the file independently. But the actual executable code should not be able to access its own comments.

    • @peereboominc@lemm.ee
      link
      fedilink
      English
      118 hours ago

      Some languages use the comments to generate documentation. Something like

      // function to add two numbers func Add(num1 int, num2 int)

  • Scrubbles
    link
    fedilink
    English
    6722 hours ago

    checks the community to make sure I’m in programmer humor

    Yeah that checks out

    • @Chais@sh.itjust.works
      link
      fedilink
      1720 hours ago

      You can so stupid shit in any language. I admit Python doesn’t exactly make it difficult. A bit like JS, but different.

      • @verdigris@lemmy.ml
        link
        fedilink
        3
        edit-2
        15 hours ago

        Being able to get the line number is very different from comments being parsed.

        Edit: didn’t realize this was custom code built to be cursed.

        • bjorney
          link
          fedilink
          13
          edit-2
          18 hours ago

          You should look at how OPs example works first maybe

          The python interpreter isn’t parsing comments, the add() function is just getting the current line number from the call stack context, and using a regex to spit out the numbers to the right of the “#” on the current executing line of the source code.

    • @justcallmelarry@lemmy.dbzer0.com
      link
      fedilink
      46
      edit-2
      21 hours ago

      The add() function (that is available in the source code) basically uses some built in debugging tools to find out where in the code the function is called, and then parses the comment from the file and uses it for adding stuff.

      I’ve never tried (becuse why would you…) but something similar can probably be built in any interpreted language

      It’s not something Python does by design

      • @N0x0n@lemmy.ml
        link
        fedilink
        9
        edit-2
        21 hours ago

        Thanks :) ! Could you tell me what use case/purpose such function can have from a dev perspective?

        • bjorney
          link
          fedilink
          920 hours ago

          This stuff is normally used for creating human readable error messages. E.g. printing the line of your code that actually set off the exception

        • @McWizard@lemmy.zip
          link
          fedilink
          419 hours ago

          We actually use method comments for user documentation as well. Only on specific business methods, but it’s nice to have a good comment for the dev and a tooltip for the user at the same time.

        • @justcallmelarry@lemmy.dbzer0.com
          link
          fedilink
          5
          edit-2
          21 hours ago

          This specific use case? To make a meme, mainly ¯\(ツ)

          As for the components: Parsing comments have been used for stuff like type hints / formatting / linting, tho generally not at run time (afaik).

          The tooling for finding out where something is called from can be used to give a better understanding of where things go wrong when an exception happens or similar, to add to logs.

          I would say that in general you don’t need either functionality except for certain edge-usecases

    • @0t79JeIfK01RHyzo@lemmy.ml
      link
      fedilink
      English
      3
      edit-2
      21 hours ago
      It does work I know it at least partially works
      class add:
           count = 0
      
           def __init__(self):
                   add.count += 1
                   self.value = add.count
           def __str__(self):
                   if self.value == 1:
                           return "3"
                   elif self.value == 2:
                           return "7"
                   else:
                           return "32"
      
      result = add()  # 1 2
      print(result)
      result = add()  # 3 4
      print(result)
      result = add()  # 3 4 5 20
      print(result)
      
      • Rikudou_SageA
        link
        English
        119 hours ago

        Eh, the original function actually parses the line that calls the function, extracts the arguments from the comment and then sums them.