Python Best Practices for a New Project in 2021

Re:Python Best Practices for a New Project in 2021 by hetspookjee on Monday July 05, 2021 @07:53AM (#27736989)

My experience is also that PyCharm is much more pleasureable to work with and on a safer side. I checked 1.5 year ago, so could be changed, for remote development on a server and had to download some 3rd party Rsync tools to be able to do so. For PyCharm is just works out of the box with a professional license.

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by 0x008 on Monday July 05, 2021 @05:19PM (#27741918)

VS Code experience has definitely improved a LOT in the past 1.5 years with the new python language server (pylance) and remote development being improved quite a bot. We use it daily in production in my company with almost zero problems so far.

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by rwmark on Monday July 05, 2021 @08:13AM (#27737140)

Indeed, anything but VSCode:

"What data is collected. The GitHub Copilot collects activity from the user's Visual Studio Code editor, tied to a timestamp, and metadata."

PyCharm, Emacs, Vim, are all better and don't spy.

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by btdmaster on Monday July 05, 2021 @09:56AM (#27738037)

PyCharm has similarly bad privacy: https://www.jetbrains.com/legal/docs/privacy/privacy.html. I'm really happy though that I learned to use Emacs, really useful and language independent.

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by excitednumber on Monday July 05, 2021 @08:49AM (#27737409)

I came here to read this.

[ Parent | on HN ]