dplyr VS polars

That's great feedback, thanks!

This tool definitely comes from a place of personal need - beyond just handling large files, I've also never really gelled well with the Excel/Google Sheet model of changing data in place as if you were editing text. I'm a Data Scientist and always preferred the chained data transforms you see in things like dplyr (https://dplyr.tidyverse.org/) or Polars (https://pola.rs/) and I feel this tool maps very closely to the chained model.

Also, thank you for the feature requests! Those would all be very useful - we'll put them on the roadmap.

There's an example of how to use zzz.R with a .onload() function to set options in the dplyr code base: https://github.com/tidyverse/dplyr/blob/bbcfe99e29fe737d456b0d7adc33d3c445a32d9d/R/zzz.r

Look at the tidyverse, especially the case_when or mutate functions.

Before diving into advanced machine learning algorithms or statistical models, we need to start with the basics: collecting and organizing data. Fortunately, both Python and R offer a wealth of libraries that make it easy to collect data from a variety of sources, including web scraping, APIs, and reading from files. Key libraries in Python include requests, BeautifulSoup, and pandas, while R has httr, rvest, and dplyr.

It looks like your syntax is wrong. I think you’re trying to calculate a new variables in your data frame, or alter an existing column in a data frame. Have a look at the select() function in this reference for the proper syntax to use. https://dplyr.tidyverse.org/ Does that help?

A lot of populat libraries have their own logos. Maybe one of them would be good. Check out dplyr for example: https://dplyr.tidyverse.org/

I hope you give it a try when you get a chance: https://dplyr.tidyverse.org/

You can read up on the dplyr-verbs here, which I strongly suggest for your exam! In the code examples, you can simply click on any function you don't understand and it will take you directly to the documentation. Good Luck!

This is because 0.1 is in actuality the floating point value value 0.1000000000000000055511151231257827021181583404541015625, and thus 1 divided by it is ever so slightly smaller than 10. Nevertheless, fpround(1 / fpround(1 / 10)) = 10 exactly.

I found out about this recently because in Polars I defined a // b for floats to be (a / b).floor(), which does return 10 for this computation. Since Python's correctly-rounded division is rather expensive, I chose to stick to this (more context: https://github.com/pola-rs/polars/issues/14596#issuecomment-...).

https://github.com/pola-rs/polars/releases/tag/py-0.19.0

That turned out to be related to pola-rs/polars#11912, and this linked comment provided a deceptively simple solution - use PARSE_DECLTYPES when creating the connection: