This blog series provides an at-a-glance roundup of recent activity within the LineaPy community, including new features, bug fixes, collaborator shout outs, github discussions or community gatherings.

NEW FEATURES!

The LineaPy team rolled out a few major changes to the main branch on LineaPy’s Github repo:

• LineaPy Configuration: We’ve implemented lineapy.options.set to enable changing the LineaPy backend database and where artifacts are saved. This is useful if you want to switch between different artifact stores (for instance if you are sharing our artifacts with someone else). This is especially helpful if you are not starting LineaPy from the command line (for instance if you are using Google Colab or hosted Jupyter Hub). With this update, you can now use a configuration file, environment variables, or CLI options to start the LineaPy instance with different configurations. Last, you can use lineapy –options init to create the configuration file and make these changes persistent without setting them every time.
  • Learn more on Config Documentation and Github Discussion.
• Walrus Operator: We have added support for the walrus operator in LineaPy. The walrus operator, := (named so as it resembles the tusks of a walrus), was introduced in Python 3.8 which enables the programmer to simultaneously assign variables in the middle of an expression, reducing repetition in code and making debugging complex expressions easier.
  • Learn more here (Github Discussion).

COMMUNITY GOODNESS

• LineaPy User Testimonial: LineaPy user Senthil E posted a comprehensive overview of LineaPy on Towards Data Science. The figures he created to illustrate various LineaPy concepts as well as use cases to illustrate the benefits of the APIs are awesome! We appreciate contributions like this to the LineaPy community. You can connect with Senthil on LinkedIn.
• LineaPy Workshop: We hosted our first-ever LineaPy Workshop on Friday, June 3. A big thank you to those who joined us. To watch the recording, visit our YouTube Channel.