We have officially started our codebase migration over to Python 3. There’s quite a lot involved in this process, which you can read all about in our Python 3 devblog!
We’re currently at the first step: migrating the code that contains pre-2.7 syntax into modern 2.7 equivalents. Today’s update doesn’t change any behaviors or introduce any compatibility issues. But, it touches a huge portion of the codebase. We’ve done extensive testing (and you’ve helped!), but we’re very interested in any issues or performance problems that you experience.
If anything feels “off”, even if you can’t fully describe it, please let us know by filing a bug report. The bug reporting tool provides us with a lot of great additional information, though if you have some questions or run into issues with the bug reporting tool we’ll be checking this thread too.
Thanks for all your help, and we’ll see you for the next update!
And also that funny list comprehension construct, where you use a variable before you define it in the for loop - “to make code shorter and easier readable”. Unbelievably bad.
Deal with it, there’s a reason any idiot without proper programmer trainning loves Python.
What is done is done, at least they decided to modernize that crap.
Don’t take it personal, if you love Python but you also know proper programming, all good. If you ONLY know Python, just like some people that ONLY knows JS. Well, you should learn programming properly then.
Lots of good programmers like Python, but they know proper languages to do the serious job when needed.
Cmon folks those client exits freeze the entire street in my neighbourhood. I got python is easier, even language choice does not really matter much these days from skills perspective as ai can program any. But for high performance multi window client it is really important to be written on something high performant. Get it done on Rust or old good C, you can do it FC!
I watched the video on blog and there was some short mentioning on memory leaks
I’m not an IT expert, so take it as a experience of me… This is how I can simulate the memory leaks, might help in possible future diagnostix.
I play on Linux through Wine (staging) and I just found out, that when I open Skill window and then I open Opportunities window, it starts memory leaks (goes up to 64gb of my DDR5 RAM and then freezes for few seconds and shuts down EVE Client and launcher as well. This all takes like 10-200 mb ram / second, so it takes few minutes to reach 64 gb.
However, when I open Options (during memory leak) and turn OFF AMD FSR 1.0, memory leaks resets and memory returns to “default” levels
When I again open windows as above mentioned, leak started again, so I turn ON AMD FSR 1.0 and again, it’s done with leak
Same with switching Upscaling setting from Ultra quality to Performance and back.
These leaks were not present until wine-staging 10.4, started in 10.5 onward.
Manjaro, KDE plasma 6.7.4, wayland, NVIdia RTX 2060 SUPER 8GB, i5-12600K, Kernel 6.18 LTS.
It does not happend on Intel arc graphics (my notebook). I have not tested on AMD graphics card, as I do not have one. I also have not tested it on X11, cause I’m lazy to switch :). Otherwise game runs smoothly.
As someone who is not a tech programmer or language reader (human anatomy is my gig)
sounds impressive what you are attempting to do @CCP_Swift and the rest of the team.
