HackerFriction Feedback

Products · Product

Python

Raised as a usability problem by 1,112 people on Hacker News over 19 years (2008–2026), in 1,005 threads.

Ranked by people · period

  1. 1
    Competing tools and versions make installing packages messyUnreviewed

    58 people in the last 5 years · 51 threads

  2. 2
    Installing packages and setting up venvs is confusing to get workingUnreviewed

    34 people in the last 5 years · 34 threads

  3. 3
    Dependency setup breaks and is hard to fix, even for simple tasksUnreviewed

    13 people in the last 5 years · 13 threads

  4. 4
    Nested list comprehensions are too confusing and hard to readUnreviewed

    11 people in the last 5 years · 10 threads

  5. 5
    Indentation-based syntax causes bugs that take long to findUnreviewed

    8 people in the last 5 years · 8 threads

  6. 6
    Syntax is too confusing to read and has caused dozens of bugsUnreviewed

    8 people in the last 5 years · 8 threads

  7. 7
    Documentation reads like reference rather than step-by-step instructionsUnreviewed

    7 people in the last 5 years · 6 threads

  8. 8
    Basic Python doc searches return junk, outdated answers and dense textUnreviewed

    7 people in the last 5 years · 7 threads

  9. 9
    No package manager understands the virtualenv, causing confusionUnreviewed

    7 people in the last 5 years · 7 threads

  10. 10
    Type-checking tools are slow, hard to use and hard to understandUnreviewed

    7 people in the last 5 years · 7 threads

  11. 11
    Users must guess parameter types without good function documentationUnreviewed

    6 people in the last 5 years · 6 threads

  12. 12
    Small language inconsistencies pile up, making it harder to learnUnreviewed

    6 people in the last 5 years · 6 threads

  13. 13
    Copy-pasted code breaks indentation, requiring manual whitespace checksUnreviewed

    5 people in the last 5 years · 5 threads

  14. 14
    Non-technical Windows users struggle to install Python and add it to PATHUnreviewed

    5 people in the last 5 years · 5 threads

  15. 15
    Non-ASCII characters cause encoding errors that lose tracebacksUnreviewed

    5 people in the last 5 years · 4 threads

  16. 16
    Variable scope confuses beginners, and scope errors only show at runtimeUnreviewed

    5 people in the last 5 years · 5 threads

  17. 17
    Too many type annotations clutter code and make it harder to readUnreviewed

    4 people in the last 5 years · 4 threads

  18. 18
    Type hints lack clear docs, stable APIs and an official checkerUnreviewed

    4 people in the last 5 years · 4 threads

  19. 19
    Calling async functions from non-async code is hard for newcomersUnreviewed

    4 people in the last 5 years · 4 threads

  20. 20
    Cryptic error messages make it hard to figure out what went wrongUnreviewed

    4 people in the last 5 years · 4 threads

  21. 21
    Same-directory module files aren't found, causing import errorsUnreviewed

    4 people in the last 5 years · 4 threads

  22. 22
    Crude type support makes typing Python code a constant struggleUnreviewed

    4 people in the last 5 years · 4 threads

  23. 23
  24. 24
    Import behaviour mixes many ways and is hard to reason aboutUnreviewed

    3 people in the last 5 years · 3 threads

  25. 25
    Setting up and entering a virtualenv takes a clumsy two-step processUnreviewed

    3 people in the last 5 years · 3 threads

  26. 26
    Significant whitespace is confusing for beginners learning to programUnreviewed

    3 people in the last 5 years · 3 threads

  27. 27
    Tracing argument types in large codebases is hard when debuggingUnreviewed

    3 people in the last 5 years · 3 threads

  28. 28
    Documentation doesn't say what type functions returnUnreviewed

    3 people in the last 5 years · 3 threads

  29. 29
    Pattern matching is unintuitive, requiring knowledge of unpacking stepsUnreviewed

    3 people in the last 5 years · 3 threads

  30. 30
    Pasting multi-line code into the REPL fails, needing a workaroundUnreviewed

    3 people in the last 5 years · 3 threads

  31. 31
    Setting up a Windows Python REPL takes many error-prone stepsUnreviewed

    3 people in the last 5 years · 3 threads

  32. 32
    Weak regex support and non-trivial file operations hurt scriptingUnreviewed

    3 people in the last 5 years · 3 threads

  33. 33
    Global package installs make installs messy and conflictingUnreviewed

    3 people in the last 5 years · 3 threads

  34. 34
    Autocomplete works poorly on large projects due to missing typesUnreviewed

    3 people in the last 5 years · 3 threads

  35. 35
    Python error messages are harder to debug than C++ template backtracesUnreviewed

    3 people in the last 5 years · 3 threads

  36. 36
    Circular imports need awkward workarounds that don't always workUnreviewed

    3 people in the last 5 years · 3 threads

  1. 1
    Competing tools and versions make installing packages messyUnreviewed

    100 people since the beginning · 89 threads

  2. 2
    Installing packages and setting up venvs is confusing to get workingUnreviewed

    48 people since the beginning · 47 threads

  3. 3
    Indentation-based syntax causes bugs that take long to findUnreviewed

    25 people since the beginning · 24 threads

  4. 4
    Documentation reads like reference rather than step-by-step instructionsUnreviewed

    24 people since the beginning · 22 threads

  5. 5
    Copy-pasted code breaks indentation, requiring manual whitespace checksUnreviewed

    23 people since the beginning · 22 threads

  6. 6
    Nested list comprehensions are too confusing and hard to readUnreviewed

    23 people since the beginning · 21 threads

  7. 7
    Users must guess parameter types without good function documentationUnreviewed

    20 people since the beginning · 20 threads

  8. 8
    Non-technical Windows users struggle to install Python and add it to PATHUnreviewed

    16 people since the beginning · 15 threads

  9. 9
    Small language inconsistencies pile up, making it harder to learnUnreviewed

    16 people since the beginning · 16 threads

  10. 10
    No package manager understands the virtualenv, causing confusionUnreviewed

    15 people since the beginning · 15 threads

  11. 11
    Dependency setup breaks and is hard to fix, even for simple tasksUnreviewed

    14 people since the beginning · 14 threads

  12. 12
    Import behaviour mixes many ways and is hard to reason aboutUnreviewed

    14 people since the beginning · 9 threads

  13. 13
    Basic Python doc searches return junk, outdated answers and dense textUnreviewed

    13 people since the beginning · 13 threads

  14. 14
    Non-ASCII characters cause encoding errors that lose tracebacksUnreviewed

    13 people since the beginning · 11 threads

  15. 15
    Syntax is too confusing to read and has caused dozens of bugsUnreviewed

    12 people since the beginning · 12 threads

  16. 16
    Too many type annotations clutter code and make it harder to readUnreviewed

    10 people since the beginning · 10 threads

  17. 17
    Significant whitespace is confusing for beginners learning to programUnreviewed

    9 people since the beginning · 9 threads

  18. 18
    Type hints lack clear docs, stable APIs and an official checkerUnreviewed

    8 people since the beginning · 8 threads

  19. 19
    Migrating from Python 2 needs painful flag-day changesUnreviewed

    8 people since the beginning · 7 threads

  20. 20
    Type-checking tools are slow, hard to use and hard to understandUnreviewed

    8 people since the beginning · 8 threads

  21. 21
    Getting local timezone-aware timestamps is unintuitive and often done wrongUnreviewed

    8 people since the beginning · 5 threads

  22. 22
    Setting up and entering a virtualenv takes a clumsy two-step processUnreviewed

    7 people since the beginning · 7 threads

  23. 23
    Mutable default arguments are shared across calls, needing a None workaroundUnreviewed

    7 people since the beginning · 7 threads

  24. 24
    Tracing argument types in large codebases is hard when debuggingUnreviewed

    7 people since the beginning · 7 threads

  25. 25
    Calling async functions from non-async code is hard for newcomersUnreviewed

    7 people since the beginning · 7 threads

  26. 26
    Finding one function means scanning a huge page of 20+ functionsUnreviewed

    7 people since the beginning · 6 threads

  27. 27
    Cryptic error messages make it hard to figure out what went wrongUnreviewed

    7 people since the beginning · 7 threads

  28. 28
    Missing conceptual docs and cross-references make asyncio hard to understandUnreviewed

    7 people since the beginning · 5 threads

  29. 29
    Too many navigation and link lists make pages hard to scanUnreviewed

    7 people since the beginning · 7 threads

  30. 30
    Documentation doesn't say what type functions returnUnreviewed

    7 people since the beginning · 6 threads

  31. 31
    Hard to tell which Python binary or version a system providesUnreviewed

    6 people since the beginning · 6 threads

  32. 32
    Variable scope confuses beginners, and scope errors only show at runtimeUnreviewed

    6 people since the beginning · 6 threads

  33. 33
    Crude type support makes typing Python code a constant struggleUnreviewed

    6 people since the beginning · 6 threads

  34. 34
    Importing a module by name requires many obscure steps and boilerplateUnreviewed

    5 people since the beginning · 5 threads

  35. 35
    Constant tinkering is required and debugging becomes very hardUnreviewed

    5 people since the beginning · 5 threads

  36. 36
    Pattern matching is unintuitive, requiring knowledge of unpacking stepsUnreviewed

    5 people since the beginning · 5 threads

  37. 37
    Same-directory module files aren't found, causing import errorsUnreviewed

    5 people since the beginning · 5 threads

  38. 38
    The else keyword on loops reads as the opposite of its usual meaningUnreviewed

    5 people since the beginning · 3 threads

  39. 39
    Pasting multi-line code into the REPL fails, needing a workaroundUnreviewed

    4 people since the beginning · 4 threads

  40. 40
    Published packages never work, and conflicting guidance adds confusionUnreviewed

    4 people since the beginning · 4 threads

  41. 41
    Metaclasses are hard for most programmers to understand and maintainUnreviewed

    4 people since the beginning · 4 threads

  42. 42
    Debug print() with parentheses causes syntax errors, forcing repeated editsUnreviewed

    4 people since the beginning · 4 threads

  43. 43
    Magic argument inference makes failures hard to diagnoseUnreviewed

    4 people since the beginning · 4 threads

  44. 44
    Decorators are barely documented, so learners can't find how to use themUnreviewed

    4 people since the beginning · 4 threads

  45. 45
    Setting up a Windows Python REPL takes many error-prone stepsUnreviewed

    4 people since the beginning · 4 threads

  46. 46
    Weak regex support and non-trivial file operations hurt scriptingUnreviewed

    4 people since the beginning · 4 threads

  47. 47
    Global package installs make installs messy and conflictingUnreviewed

    4 people since the beginning · 4 threads

  48. 48
    Standard code silently blocks the event loop and is hard to avoidUnreviewed

    4 people since the beginning · 4 threads

  49. 49
    Editor re-indenting silently changes program output with no errorUnreviewed

    4 people since the beginning · 4 threads

  50. 50
    Many overlapping ways to do the same thing confuse usersUnreviewed

    4 people since the beginning · 4 threads

  51. 51
    Building UIs with Qt, WX, GTK or Tkinter is hard and unpleasantUnreviewed

    4 people since the beginning · 4 threads

  52. 52
    Typing quit shows a message instead of exiting, requiring quit() or Ctrl-DUnreviewed

    4 people since the beginning · 4 threads

  53. 53
  54. 54
    Tools wreck shell profiles and silently use wrong package versionsUnreviewed

    3 people since the beginning · 3 threads

  55. 55
    Piping output between processes causes buffering deadlocksUnreviewed

    3 people since the beginning · 3 threads

  56. 56
    Step debuggers in Python editors are buggy and clumsy beside the REPLUnreviewed

    3 people since the beginning · 3 threads

  57. 57
    Piping commands and conditionals is verbose without third-party librariesUnreviewed

    3 people since the beginning · 3 threads

  58. 58
  59. 59
    Beginners see nothing happen after Enter when brackets are unclosedUnreviewed

    3 people since the beginning · 3 threads

  60. 60
    Beginners must absorb confusing, unneeded constructs in their first programUnreviewed

    3 people since the beginning · 3 threads

  61. 61
    Bytes and str mismatch makes handling binary data tedious and error-proneUnreviewed

    3 people since the beginning · 3 threads

  62. 62
    Reloading changed functions interactively often runs old codeUnreviewed

    3 people since the beginning · 3 threads

  63. 63
    map() returns a generator, so users must wrap list() to get a listUnreviewed

    3 people since the beginning · 3 threads

  64. 64
    Zero-based indexing and exclusive slice ends feel unintuitive to learnersUnreviewed

    3 people since the beginning · 3 threads

  65. 65
  66. 66
    Users gave up on libraries because they couldn't work out usageUnreviewed

    3 people since the beginning · 3 threads

  67. 67
  68. 68
    Wrong-typed inputs are silently reinterpreted, hiding bugsUnreviewed

    3 people since the beginning · 3 threads

  69. 69
  70. 70
    Ubuntu ships without working pip or virtualenv, forcing root installsUnreviewed

    3 people since the beginning · 3 threads

  71. 71
    Hard to debug when objects fail to pickle during interprocess communicationUnreviewed

    3 people since the beginning · 3 threads

  72. 72
    Sidebar styling pulls the eye away from main text while readingUnreviewed

    3 people since the beginning · 3 threads

  73. 73
    Autocomplete works poorly on large projects due to missing typesUnreviewed

    3 people since the beginning · 3 threads

  74. 74
    Hard to get into and hard to read other people's Python codeUnreviewed

    3 people since the beginning · 3 threads

  75. 75
    Overlapping string formatting methods make code hard to readUnreviewed

    3 people since the beginning · 3 threads

  76. 76
    str.join syntax is unintuitive and confusing to newcomersUnreviewed

    3 people since the beginning · 3 threads

  77. 77
    Python error messages are harder to debug than C++ template backtracesUnreviewed

    3 people since the beginning · 3 threads

  78. 78
    Circular imports need awkward workarounds that don't always workUnreviewed

    3 people since the beginning · 3 threads

  79. 79
    Generics need separate TypeVar declarations, which is awkward to useUnreviewed

    3 people since the beginning · 3 threads

Every issue, all time, most people first

  1. Competing tools and versions make installing packages messyUnreviewed

    100 people since 2010, in 16 different years · 5 this year

    2008: 0 people2009: 0 people2010: 2 people2011: 2 people2012: 3 people2013: 1 person2014: 1 person2015: 0 people2016: 2 people2017: 3 people2018: 6 people2019: 7 people2020: 4 people2021: 18 people2022: 10 people2023: 16 people2024: 10 people2025: 14 people2026: 3 people
    20082026
    Something wrong here?
  2. Installing packages and setting up venvs is confusing to get workingUnreviewed

    48 people since 2012, in 14 different years · 4 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 2 people2015: 1 person2016: 2 people2017: 1 person2018: 2 people2019: 2 people2020: 2 people2021: 3 people2022: 8 people2023: 10 people2024: 6 people2025: 8 people2026: 2 people
    20082026
    Something wrong here?
  3. Indentation-based syntax causes bugs that take long to findUnreviewed

    25 people since 2008, in 16 different years · 1 this year

    2008: 1 person2009: 2 people2010: 1 person2011: 2 people2012: 0 people2013: 0 people2014: 1 person2015: 1 person2016: 1 person2017: 4 people2018: 1 person2019: 2 people2020: 1 person2021: 1 person2022: 3 people2023: 2 people2024: 2 people2025: 0 people2026: 1 person
    20082026
    Something wrong here?
  4. Documentation reads like reference rather than step-by-step instructionsUnreviewed

    24 people since 2012, in 11 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 2 people2014: 1 person2015: 2 people2016: 3 people2017: 3 people2018: 0 people2019: 0 people2020: 2 people2021: 4 people2022: 1 person2023: 3 people2024: 2 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  5. Copy-pasted code breaks indentation, requiring manual whitespace checksUnreviewed

    23 people since 2009, in 13 different years · 1 this year

    2008: 0 people2009: 1 person2010: 1 person2011: 0 people2012: 0 people2013: 0 people2014: 5 people2015: 1 person2016: 1 person2017: 1 person2018: 3 people2019: 3 people2020: 4 people2021: 0 people2022: 2 people2023: 0 people2024: 1 person2025: 1 person2026: 1 person
    20082026
    Something wrong here?
  6. Nested list comprehensions are too confusing and hard to readUnreviewed

    23 people since 2011, in 12 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 2 people2016: 2 people2017: 1 person2018: 3 people2019: 2 people2020: 2 people2021: 0 people2022: 4 people2023: 2 people2024: 2 people2025: 2 people2026: 1 person
    20082026
    Something wrong here?
  7. Users must guess parameter types without good function documentationUnreviewed

    20 people since 2009, in 13 different years · none this year

    2008: 0 people2009: 1 person2010: 0 people2011: 0 people2012: 1 person2013: 1 person2014: 1 person2015: 1 person2016: 2 people2017: 1 person2018: 3 people2019: 1 person2020: 1 person2021: 1 person2022: 5 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  8. Non-technical Windows users struggle to install Python and add it to PATHUnreviewed

    16 people since 2010, in 9 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 1 person2012: 4 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 3 people2021: 1 person2022: 0 people2023: 2 people2024: 2 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  9. Small language inconsistencies pile up, making it harder to learnUnreviewed

    16 people since 2008, in 8 different years · 3 this year

    2008: 1 person2009: 0 people2010: 0 people2011: 0 people2012: 2 people2013: 1 person2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 3 people2020: 1 person2021: 2 people2022: 0 people2023: 3 people2024: 0 people2025: 0 people2026: 3 people
    20082026
    Something wrong here?
  10. No package manager understands the virtualenv, causing confusionUnreviewed

    15 people since 2014, in 8 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 3 people2017: 1 person2018: 0 people2019: 2 people2020: 1 person2021: 0 people2022: 1 person2023: 5 people2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  11. Import behaviour mixes many ways and is hard to reason aboutUnreviewed

    14 people since 2016, in 8 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 1 person2018: 1 person2019: 1 person2020: 1 person2021: 7 people2022: 2 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  12. Dependency setup breaks and is hard to fix, even for simple tasksUnreviewed

    14 people since 2019, in 5 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 0 people2022: 3 people2023: 4 people2024: 4 people2025: 2 people2026: 0 people
    20082026
    Something wrong here?
  13. Basic Python doc searches return junk, outdated answers and dense textUnreviewed

    13 people since 2013, in 9 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 1 person2016: 0 people2017: 1 person2018: 1 person2019: 0 people2020: 0 people2021: 4 people2022: 1 person2023: 2 people2024: 1 person2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  14. Non-ASCII characters cause encoding errors that lose tracebacksUnreviewed

    13 people since 2013, in 7 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 2 people2016: 2 people2017: 0 people2018: 3 people2019: 1 person2020: 0 people2021: 0 people2022: 2 people2023: 3 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  15. Syntax is too confusing to read and has caused dozens of bugsUnreviewed

    12 people since 2014, in 7 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 2 people2019: 1 person2020: 0 people2021: 1 person2022: 2 people2023: 3 people2024: 2 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  16. Too many type annotations clutter code and make it harder to readUnreviewed

    10 people since 2012, in 9 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 1 person2015: 0 people2016: 1 person2017: 0 people2018: 1 person2019: 1 person2020: 1 person2021: 0 people2022: 1 person2023: 2 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  17. Significant whitespace is confusing for beginners learning to programUnreviewed

    9 people since 2011, in 6 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 1 person2021: 3 people2022: 2 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  18. Type hints lack clear docs, stable APIs and an official checkerUnreviewed

    8 people since 2016, in 7 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 1 person2019: 1 person2020: 1 person2021: 0 people2022: 1 person2023: 1 person2024: 2 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  19. Migrating from Python 2 needs painful flag-day changesUnreviewed

    8 people since 2010, in 7 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 2 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  20. Getting local timezone-aware timestamps is unintuitive and often done wrongUnreviewed

    8 people since 2012, in 6 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 1 person2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 1 person2022: 4 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  21. Type-checking tools are slow, hard to use and hard to understandUnreviewed

    8 people since 2016, in 5 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 3 people2023: 0 people2024: 1 person2025: 2 people2026: 1 person
    20082026
    Something wrong here?
  22. Setting up and entering a virtualenv takes a clumsy two-step processUnreviewed

    7 people since 2013, in 7 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 1 person2015: 0 people2016: 0 people2017: 1 person2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 1 person2023: 0 people2024: 0 people2025: 1 person2026: 1 person
    20082026
    Something wrong here?
  23. Mutable default arguments are shared across calls, needing a None workaroundUnreviewed

    7 people since 2010, in 6 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 2 people2022: 0 people2023: 0 people2024: 1 person2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  24. Tracing argument types in large codebases is hard when debuggingUnreviewed

    7 people since 2010, in 6 different years · 2 this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 1 person2018: 1 person2019: 0 people2020: 1 person2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 2 people
    20082026
    Something wrong here?
  25. Calling async functions from non-async code is hard for newcomersUnreviewed

    7 people since 2012, in 6 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 1 person2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 1 person2023: 1 person2024: 0 people2025: 2 people2026: 0 people
    20082026
    Something wrong here?
  26. Finding one function means scanning a huge page of 20+ functionsUnreviewed

    7 people since 2010, in 6 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 2 people2013: 1 person2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  27. Cryptic error messages make it hard to figure out what went wrongUnreviewed

    7 people since 2013, in 5 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 2 people2022: 1 person2023: 2 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  28. Missing conceptual docs and cross-references make asyncio hard to understandUnreviewed

    7 people since 2015, in 5 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 1 person2016: 3 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 1 person2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  29. Documentation doesn't say what type functions returnUnreviewed

    7 people since 2016, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 2 people2017: 0 people2018: 0 people2019: 0 people2020: 2 people2021: 0 people2022: 1 person2023: 2 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  30. Hard to tell which Python binary or version a system providesUnreviewed

    6 people since 2016, in 6 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 1 person2018: 0 people2019: 1 person2020: 1 person2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  31. Variable scope confuses beginners, and scope errors only show at runtimeUnreviewed

    6 people since 2019, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 0 people2022: 1 person2023: 2 people2024: 0 people2025: 2 people2026: 0 people
    20082026
    Something wrong here?
  32. Crude type support makes typing Python code a constant struggleUnreviewed

    6 people since 2019, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 2 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 2 people2025: 2 people2026: 0 people
    20082026
    Something wrong here?
  33. Importing a module by name requires many obscure steps and boilerplateUnreviewed

    5 people since 2013, in 5 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 1 person2023: 0 people2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  34. Constant tinkering is required and debugging becomes very hardUnreviewed

    5 people since 2016, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 2 people2019: 1 person2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  35. Pattern matching is unintuitive, requiring knowledge of unpacking stepsUnreviewed

    5 people since 2021, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 2 people2022: 1 person2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  36. Same-directory module files aren't found, causing import errorsUnreviewed

    5 people since 2021, in 4 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 1 person2024: 2 people2025: 0 people2026: 1 person
    20082026
    Something wrong here?
  37. The else keyword on loops reads as the opposite of its usual meaningUnreviewed

    5 people since 2014, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 1 person2018: 3 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  38. Pasting multi-line code into the REPL fails, needing a workaroundUnreviewed

    4 people since 2012, in 4 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 1 person2025: 0 people2026: 1 person
    20082026
    Something wrong here?
  39. Published packages never work, and conflicting guidance adds confusionUnreviewed

    4 people since 2019, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 1 person2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  40. Metaclasses are hard for most programmers to understand and maintainUnreviewed

    4 people since 2012, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 1 person2016: 0 people2017: 1 person2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  41. Debug print() with parentheses causes syntax errors, forcing repeated editsUnreviewed

    4 people since 2012, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 1 person2016: 1 person2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  42. Magic argument inference makes failures hard to diagnoseUnreviewed

    4 people since 2016, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 1 person2019: 0 people2020: 1 person2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  43. Decorators are barely documented, so learners can't find how to use themUnreviewed

    4 people since 2011, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  44. Setting up a Windows Python REPL takes many error-prone stepsUnreviewed

    4 people since 2021, in 4 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 1 person2024: 1 person2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  45. Weak regex support and non-trivial file operations hurt scriptingUnreviewed

    4 people since 2012, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 1 person2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  46. Global package installs make installs messy and conflictingUnreviewed

    4 people since 2010, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 1 person2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  47. Standard code silently blocks the event loop and is hard to avoidUnreviewed

    4 people since 2016, in 4 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 1 person2026: 1 person
    20082026
    Something wrong here?
  48. Editor re-indenting silently changes program output with no errorUnreviewed

    4 people since 2011, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 1 person2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 1 person2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  49. Many overlapping ways to do the same thing confuse usersUnreviewed

    4 people since 2019, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 1 person2021: 1 person2022: 0 people2023: 0 people2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  50. Building UIs with Qt, WX, GTK or Tkinter is hard and unpleasantUnreviewed

    4 people since 2008, in 4 different years · none this year

    2008: 1 person2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 1 person2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  51. Typing quit shows a message instead of exiting, requiring quit() or Ctrl-DUnreviewed

    4 people since 2012, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  52. Unclear which metadata file to use, since pyproject.toml lacks setup.cfg contentUnreviewed

    4 people since 2023, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 2 people2024: 2 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  53. Tools wreck shell profiles and silently use wrong package versionsUnreviewed

    3 people since 2016, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  54. Piping output between processes causes buffering deadlocksUnreviewed

    3 people since 2020, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 1 person2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  55. Step debuggers in Python editors are buggy and clumsy beside the REPLUnreviewed

    3 people since 2011, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  56. Piping commands and conditionals is verbose without third-party librariesUnreviewed

    3 people since 2018, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 1 person2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  57. Explicit self parameter confuses newcomers learning object-oriented programmingUnreviewed

    3 people since 2008, in 3 different years · none this year

    2008: 1 person2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  58. Beginners see nothing happen after Enter when brackets are unclosedUnreviewed

    3 people since 2010, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  59. Beginners must absorb confusing, unneeded constructs in their first programUnreviewed

    3 people since 2011, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 0 people2022: 1 person2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  60. Bytes and str mismatch makes handling binary data tedious and error-proneUnreviewed

    3 people since 2014, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  61. Reloading changed functions interactively often runs old codeUnreviewed

    3 people since 2019, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 1 person2021: 0 people2022: 1 person2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  62. map() returns a generator, so users must wrap list() to get a listUnreviewed

    3 people since 2013, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  63. Zero-based indexing and exclusive slice ends feel unintuitive to learnersUnreviewed

    3 people since 2013, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  64. Iteration options are clumsy, with limited comprehensions and primitive iteratorsUnreviewed

    3 people since 2013, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 1 person2016: 0 people2017: 1 person2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  65. Users gave up on libraries because they couldn't work out usageUnreviewed

    3 people since 2009, in 3 different years · 1 this year

    2008: 0 people2009: 1 person2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 1 person2025: 0 people2026: 1 person
    20082026
    Something wrong here?
  66. Windows download choices confuse, including Python 2 versus 3 and installer variantsUnreviewed

    3 people since 2011, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  67. Wrong-typed inputs are silently reinterpreted, hiding bugsUnreviewed

    3 people since 2020, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 1 person2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  68. Renaming variables is manual and error-prone, with no help finding definitionsUnreviewed

    3 people since 2010, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  69. Ubuntu ships without working pip or virtualenv, forcing root installsUnreviewed

    3 people since 2014, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  70. Hard to debug when objects fail to pickle during interprocess communicationUnreviewed

    3 people since 2014, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  71. Autocomplete works poorly on large projects due to missing typesUnreviewed

    3 people since 2023, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 1 person2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  72. Hard to get into and hard to read other people's Python codeUnreviewed

    3 people since 2015, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 2 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  73. Overlapping string formatting methods make code hard to readUnreviewed

    3 people since 2016, in 2 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 2 people2026: 0 people
    20082026
    Something wrong here?
  74. str.join syntax is unintuitive and confusing to newcomersUnreviewed

    3 people since 2009, in 2 different years · none this year

    2008: 0 people2009: 2 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  75. Python error messages are harder to debug than C++ template backtracesUnreviewed

    3 people since 2022, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 1 person2023: 0 people2024: 0 people2025: 2 people2026: 0 people
    20082026
    Something wrong here?
  76. Circular imports need awkward workarounds that don't always workUnreviewed

    3 people since 2022, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 2 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  77. Generics need separate TypeVar declarations, which is awkward to useUnreviewed

    3 people since 2021, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 2 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?

This list counts all time; the period switch above only changes the ranking. Each issue is a group of similar complaints raised by at least 3 people in 3 different months and threads. Each line under an issue is Claude Haiku's summary of one of its latest comments, not a quote; follow it to read the comment on Hacker News.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 50 complaints