DataGrip and Database Tools UX Survey #2
#Python #Pycharm
https://blog.jetbrains.com/datagrip/2025/05/13/datagrip-and-database-tools-ux-survey-2/

DataGrip and Database Tools UX Survey #2
#Python #Pycharm
https://blog.jetbrains.com/datagrip/2025/05/13/datagrip-and-database-tools-ux-survey-2/
7 Course-Bundle: Shut Up and Code Python + PyCharm + Coding Interview + Machine Learning + One-Liners + Regex + Lambdas http://leanpub.com/set/leanpub/7courses is the featured Track of online courses on the Leanpub homepage! https://leanpub.com #ComputerProgramming #Devops #python #pycharm
What's going on with recent versions of #PyCharm?
#JetBrains has managed to screw up their requirements.txt implementation quite badly. This is a fundamental feature - how could they ship something so broken????
First, the virtualenv would be built with the latest versions of all the packages and not the specified pinned versions in requirements.txt! An absolutely fundamental feature completely broken.
Second, for #Django development, I use the psycopg binary using the standard “psycopg[binary]==3.2.3” and PyCharm doesn't install the requested binary.
Thirdly, and not so important, but a nice lost feature - PyCharm used to flag out-of-date packages in requirements.txt in a nice, obvious manner. No longer!
Some links to the problems:
https://youtrack.jetbrains.com/issue/PY-79903/PyCharm-ignores-package-versions-from-requirements.txt
As a #programmer but #beginner I already know that documentation is important: that's why I'll make a website to document my adventures and potential progress.
If you have any resources that you think could help me, do not hesitate a second!
If you have any tools to advise, do not hesitate a second!
I'm considering using #fedora #Kinoite with #toolbx or something like #RockyLinux (but if you have other distros to advise, tell me) with
#kdevelop #codelite for C++, #spyder or #pycharm for Python
and #rustrover or #lapce for Rust
and
#kateeditor for simple file edition.
#programmers #programming #programmation #coding #coders #coders #python #cpp #Rust #rustlang #linux #foss #fosstodon #floss #flosstodon #Dev #devlog #devlife #devloper #devlopers
While I "burned" my quota of my AI Pro subscription for #pycharm within a day, my new shiny AI Ultimate subscription seems to be endless in comparison. 7 days in, and I am still way above 75%.
Love to work with these ladies - we made a great team #JetBrains #PyCharm #PyConDE
deleting all the past versions' cnfigurations in $HOME/.config/pycharm-community/
and deleting the github.xml
& gitlab.xml
fixed it for precisely 1 session.
Then #PyCharm was broken again.
Does anyone out there use #Jetbrains #PyCharm? If so, thoughts on free vs pro? (I know there’s a 30 day trial.)
@jetbrains this is espechally annoying since it applies not just to #GitHub and #GitLab but also other private servers...
Who at @jetbrains do I have to yell at so their #snap - delivered version of #PyCharm Community Edition doesn't randomly forget login credentials and when I add them in it's stuck on a loading popup to "save credentials"...
PyCharm, the Only Python IDE You Need
PyCharm is now one unified product, and your Pro license works just as it always has.
In this version, we’ve combined PyCharm Community and Professional into a single product, PyCharm. This makes it easier for all users to access the features they need without having to switch editions.
Spent some time to tweak my AI prompt for commit messages in #pycharm a bit. Now I am totally happy with it. Good* commit messages are now just a click away for me.
*) What I consider a good commit message of course.
Where the agent also shines is for questions like „What can I improve in the project?“ or „Any suggestions to implement the token generation in a more secure way?“ You normally get very detailed responses, that contain mostly valuable and solid advice.
This morning I took a different approach - I implement the logic and let the agent write the test code including some edge cases. The AI chat was used to research some topics. This worked out better, costed less tokens and I finished this in less time. I feel confirmed in my opinion about vibe coding, which I wanted to validate with a complete session.
Spent some time to reflect the vibe coding session from yesterday with Junie and Claude Code. Looking at the results of the „start from zero and just vibe along“-approach it was a failure. The result was not useable, contained hard to spot errors covered by monkey patched test code.
Junie did mostly a great job, but where it failed miserabily was, when I asked it to integrate django-templated-email-md. I did a subtle typo and just asked for django-templated-mail-md. The result is, that it created disfunctional code that almost looked like it could work and followed the README of the correct project. But the main import included my typo and to solve the tests, Junie mocked almost everything to run tests successully.
Just checked, Claude Code did the same.
Done for today. My AI quota is almost used for this month. I did the same tasks over the evening with claude code too. Effectively this experiment costed $15, so it is fair that my monthly quota with Jetbrains is consumed. Jetbrains AI costs $10 on the Pro plan.
I have to review the docs tomorrow, then I am actually ready to release this library.