I appreciate your patience! PrettyTables.jl v3 is finally complete
Tomorrow, I’ll tag it and initiate the PR to update DataFrames.jl. From the user’s perspective, DataFrames.jl will retain its current appearance in both text and HTML formats (except when you use show to customize the PrettyTables.jl output, in which case many things will break).
Thank you for v3. Reads like it was a lot of work and sets it up for future maintainability.
Is there an example of translating functions/API calls from v2.4.0 to v3.x?
We find the changelog lacking in such documentation. The v3 release only mentions * This new version contains many breaking changes; and, the git diff between v2.4 and v3 is massive.
We use PrettyTables in thousands of julia programs. The update from v2 to v3 breaks all of them in various ways. We’ve currently pinned v2.4.0 to avoid hundreds of people re-writing their code. However, we’d like to write a meta-script to catch/update some common API changes.
For example, 384 programs use @pt macro, but this doesn’t exist in v3.x; that we can find. And around 1,100 programs use tf=tf_html_dark or some variation of the old tf format. It was so nice to just call tf_html_dark and have it just work.
For now, I’ve forked PrettyTables at v2.4.0 and called it PrettyTablesv2 and have instructed devs to use our own module from our package registry until they can get around to updating their code. I’m probably going to have to update all the code from past postdocs and devs that left the org.
Thank you @ronis_br for this wonderful package.
I update to 3.0.10 today but went back to 2.4.0 immediatly after realizing (like @sampope) we use the @pt macro in almost every scripts or projects that uses DataFrames (hundreds of files in our shared folder).
Is there any plan to implement this macro again in v3 ? It’s a great combo with DataFramesMeta.jl and Chain.jl macros…