Thanks for sharing. We use all pytest-style tests using pytest fixtures. I'll keep my eyes open for memory issues when we test upgrading to python 3.12+.
Very helpful info!
I'm most excited about the new REPL. I'm going to push for 3.13 upgrade as soon as we can (hipefully early next year). I've messed around with rc1 and the REPL is great.
Do you know why pytest was taking up so much RAM? We are also on 3.11 and I'm probably going to wait until 3.13 is useable for us.
EOL for 3.8 is coming up in a few short weeks!
So cool!! Mercury is definitely the most mysterious inner planet due to its difficulty to get a space probe there even though it's the closest planet.
The spacecraft will arrive next year, and I can't wait for all the Science it will uncover!
Haha, I've been waiting for the 4K/8K reference in this volume. Poor Anna.
The complainant suggested other manga to replace the series such as Chainsaw Man, To Your Eternity, and The Seven Deadly Sins among others.
lol
I also like the POSIX “seconds since 1970” standard, but I feel that should only be used in RAM when performing operations (time differences in timers etc.). It irks me when it’s used for serialising to text/JSON/XML/CSV.
I've seen bugs where programmers tried to represent date in epoch time in seconds or milliseconds in json. So something like "pay date" would be presented by a timestamp, and would get off-by-one errors because whatever time library the programmer was using would do time zone conversions on a timestamp then truncate the date portion.
If the programmer used ISO 8601 style formatting, I don't think they would have included the timepart and the bug could have been avoided.
Use dates when you need dates and timestamps when you need timestamps!
Do you use it? When?
Parquet is really used for big data batch data processing. It's columnar-based file format and is optimized for large, aggregation queries. It's non-human readable so you need a library like apache arrow to read/write to it.
I would use parquet in the following circumstances (or combination of circumstances):
- The data is very large
- I'm integrating this into an analytical query engine (Presto, etc.)
- I'm transporting data that needs to land in an analytical data warehouse (Snowflake, BigQuery, etc.)
- Consumed by data scientists, machine learning engineers, or other data engineers
Since the data is columnar-based, doing queries like select sum(sales) from revenue is much cheaper and faster if the underlying data is in parquet than csv.
The big advantage of csv is that it's more portable. csv as a data file format has been around forever, so it is used in a lot of places where parquet can't be used.
Wow everyone seems to love P3 but I actually liked P4 better. I mean I really enjoyed both, but P4 was a more immersive experience for me. I should reboot my vita and play it again.
I really felt like P4 had deeper connections and relationships between the characters. It felt more real, and that made the tension in the game more exciting. I love every second of it and am still trying to find a game like it.
Don't get me wrong, P3 was great also. The gameplay was superb and the characters were all great. But P4 still has a special place in my heart.
The autocomplete is nice but I don't find it a game-changer. The comment about writing tests is on point though, but that's the only place I found out useful.
Welcome to the world of light novels (and their adaptations).
They're asking for TV manufacturers to block a VPN app in the TV. Not to block VPN in general.
Hadn't realized what a banger this season is for me as a SOL/RomCom lover. Just caught up with Makeine, Alya, and Gimai Seikatsu. I'll probably pick up Giji Harem after it all airs. I usually watch 4-5 shows per year, so having 4 in one season is great.
Dude, if you're being obtuse on purpose because you have an ax to grind against Rust, try a different approach. You're not getting anywhere, clearly by the fact that no one agrees with you.
If you don't like that Rust has a restricted trademark, then call that out instead of trying to label the software and it's license as non-free. It's literally called out in my source that name restrictions ipso facto does not violate freedom 3.
But if you genuinely believe that the implementation of the Rust language and it's trademark is burdensome to create a fork, and you want people to believe you, then you gotta bring receipts. Remember, the benchmark that we both quoted is that it "effectively hampers you from releasing your changes". It being "not a piece of cake" doesn't cut it.
Hint: Google Rust forks since their existence also undermines your claim.
Good luck.
Please read this and try again.
https://www.gnu.org/philosophy/free-sw.en.html#packaging
Rules about how to package a modified version are acceptable, if they don't substantively limit your freedom to release modified versions, or your freedom to make and use modified versions privately. Thus, it is acceptable for the license to require that you change the name of the modified version, remove a logo, or identify your modifications as yours. As long as these requirements are not so burdensome that they effectively hamper you from releasing your changes, they are acceptable; you're already making other changes to the program, so you won't have trouble making a few more.
Python does not follow semver.
https://docs.python.org/3/faq/general.html#how-does-the-python-version-numbering-scheme-work
If you are being intentional about its use, then you can get a lot out of it. But for some, maybe even most, YouTube is a distraction.
Here's a hypothetical scenario at a company: We have 2 repos that builds and deploys code as tools and libraries for other apps at the company. Let's call this lib1 and lib2.
There's a third repo, let's call it app, that is application code that depends on lib1 and lib2.
The hard part right now is keeping track of which version of lib1 and lib2 are packaged for app at any point in time.
I'd like to know at a glance, say 1 month ago, what versions of app is deployed and what version of lib1 and lib2 they were using. Ideally, I'm looking for a software solution that would be agnostic to any CI/CD build system, and doubly ideally, an open source one. Maybe a simple web service you call with some metadata, and it displays it in a nice UI.
Right now, we accomplish this by looking at logs, git commit history, and stick things together. I know I can build a custom solution pretty easily, but I'm looking for something more out-of-the-box.
Trying to make web applications federated is a popular effort. Examples include things like the “fediverse”, as well as various other efforts, like attempts to make distributed software forges, and so on. However, all of these efforts suffer from a problem which is fundamental in building federated applications built on top of the web platform.
The problem is fundamentally this: when building an application on top of the web platform, an HTTP URL inherently couples an application and a resource.
The sidebar for our instance has a broken link for programming.dev - it links to https://programming.dev/programming.dev
Seth Michael Larson pointed out that the Python gzip module can be used as a CLI tool like this:
For varying levels of seniority, from senior, to staff, and beyond.
I generally don't like "listicles", especially ones that try to make you feel bad by suggesting that you "need" these skills as a senior engineer.
However, I do find this list valuable because it serves as a self-reflection tool.
Here are some areas I am pretty weak in:
- How to write a design doc, take feedback, and drive it to resolution, in a reasonable period of time
- How to convince management that they need to invest in a non-trivial technical project
- How to repeat yourself enough that people start to listen
Anything here resonate with y'all?
Read Please Go Home, Akutsu-san! Ch. 144 on MangaDex!
Jim @programming.dev I like programming and anime.
I manage the bot /u/mahoro@lemmy.ml