5% of 666 Python repos had comma typo bugs (inc V8, TensorFlow and PyTorch)

Post by [deleted] » Sat, Jan 08, 2022, 11:27 PM UTC

bcrl wrote: post #24

jollybean wrote: post #16

Earlier quoted context omitted.

5% of 'released' software is quite a lot, more importantly it's a class of errors that definitely should not exist. This is a 'bug' in the language effectively there just isn't any real upside. Python has a few of these things, which is really sad.

It's a class of error that would be caught by even the most basic testing. A better title for the article is that 5% of 666 Python repos have typos that demonstrate the code in them that is completely untested. It doesn't matter which language it is: untested code is untested code in any language.

Post by gilch » Sun, Jan 09, 2022, 5:41 AM UTC

kazinator wrote: post #140

NoahTheDuke wrote: post #131

Earlier quoted context omitted.

> Another one is having to import everything you use. The alternative is what exactly? Have the entire standard library exposed at once? Make all modules create non-conflicting names for exported objects, so that the json parse function has to be called json_parse and the csv parse function has to be called csv_parse? Seems less than ideal to me.

That's one way. If these things are classes in a plain old single-dispatch oop system, you can havec a json-parser and csv-parser which have parse methods. There could be packages/namespaces. So csv:parse and json:parse. These packages are standard and so they just exist; nothing to import. In Python, you cannot use anything without an import! The top-level modules (which serve as de facto namespaces) themselves are…

Post by usrbinbash » Mon, Jan 10, 2022, 8:45 AM UTC

animal_spirits wrote: post #220

pmarreck wrote: post #212

Earlier quoted context omitted.

Except exit. I knew Python wasn't for me in my first foray into it when I fired its REPL and then went to exit it with control-C or whatever and it literally printed out the right way to do it but then didn't do it. Python was more interested in having me do things a certain way even when it knew what I intended to do, just to be a twit .

Ctrl-c raises a KeyboardInterrupt error, which is useful for programs to catch. If you type >>> exit Use exit() or Ctrl-D (i.e. EOF) to exit You will get that error response. The goal of this is to have the REPL language the exact same as the scripting language. exit() is supposed to be called as a function to make the language more consistent, so just typing `exit` will do nothing

    import signal
    signal.signal(signal.SIGINT, throwException())

    import threading
    import time
    def sleepN():
        for i in range(20):
            time.sleep(1)
    threading.Thread(target=sleepN).start()
    time.sleep(20)

Post by rstuart4133 » Sun, Jan 16, 2022, 8:11 AM UTC

aeturnum wrote: post #213

ehsankia wrote: post #203

Earlier quoted context omitted.

A lot of people in this thread are using this to make fun of Python, but the exact same issue exists in something like c++, here's some I fixed recently: https://github.com/UWQuickstep/quickstep/pull/9 https://github.com/tensorflow/tensorflow/pull/51578 https://github.com/mono/mono/pull/21197 https://github.com/llvm/llvm-project/pull/335

I didn't understand anyone to be saying that Python is the only language to have this flaw. Also, I personally don't mind this approach to string concatenation. I think it's a fine compromise between easy formatting and clarity. I was whining about a corner case of tuple construction - which as far as I know is not a feature of any other language.

    (
       "one",
       (
          "a very very"
          "long long two"
       ),
       "three"
    )