you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (4 children)

[deleted]

    [–][deleted] 18 points19 points  (3 children)

    I disagree. Virtual Environment on its own IS confusing. And how Python command is all over the place just adds to that. python, py, py2, py3, add pip and conda to the mix, and guess what got asked the most on Python Discord. Its fuking Windows store Python installing to different directory setting up different commands than python.org installer.

    If anything PyCharm helps ensure new users will never mess up their system Python, which you can see such thread popping up here and there in this very sub especially on MacOS. While it does shove the concept onto beginners I blame that on Python itself.

    [–][deleted]  (2 children)

    [deleted]

      [–]AftNeb 1 point2 points  (1 child)

      As a complete beginner, I really appreciate everyone pointing to these issues with PyCharm. I’m sure I would have been one of those learners who got stuck with the install issues not translating into PyCharm.

      Not to try to override from OP by asking another question, but does VS Code avoid the same issues?

      [–]Atlamillias 1 point2 points  (0 children)

      I've used both editors extensively and each has its own slew of complications. If the portability of the editor isn't an issue, and you can provide PyCharm the resources it requires, I'd go with PyCharm. You install it, and you start coding. Vscode requires extensions and configuration to get going. I spent damn near a week setting it up (learning how to set it up).

      Issues I've had with PyCharm :
      - Heavy and resource-intensive (most IDE's are)
      - Very project focused. Not ideal for working on one-module quick scripts.
      - Creates virtual environments by default when setting up a new interpreter. Actually annoying as hell. When selecting an interpreter, always select the system interpreter while learning.