Version 1.0.0

kmcgrady · October 5, 2021, 3:58pm

Release date: Oct 5, 2021

Highlights

Announcing Streamlit 1.0! To read more about check out our 1.0 blog post

Other Changes

Fixed an issue where using df.dtypes to show datatypes for a DF fails while using Arrow (#3709), Image captions stay within image width and are readable (#3530)

Fhireman · October 5, 2021, 5:25pm

Congrats with the 1.0 release!!

I’m very much looking forward to a lot of things on the new roadmap. Super excited to see it!
A bunch of new widgets, multipage apps, notification toasts, the tabs container, more customization(and more developer control over widgets like to disable the “view fullscreen” interactivity of an image for example, centering an image or fully disabling the hamburger menu), URL params, are all very high up my wishlist so I really can’t wait for future releases

Thanks for all the hard work everyone has put in so far, it’s quite the awesome project!

ericgitonga · October 5, 2021, 7:18pm

Ready to rumble!

godot63 · October 6, 2021, 5:43am

This is fantastic news! thanks so much for your excellent work!

randyzwitch · October 6, 2021, 2:30pm

Hi @ryanlampkin, welcome to the Streamlit community!

I believe the behaviors you are describing are a bug that we discovered yesterday:

github.com/streamlit/streamlit

Session state setting failing to propagate to frontend

opened 12:06AM - 06 Oct 21 UTC

AnOctopus

bug state widgets

https://discuss.streamlit.io/t/problems-with-the-new-widget-behaviour-under-stre…amlit-0-89-0/17625 I investigated using the script from the post. The value seen in session state itself is being set correctly, but `should_set_frontend_state_value` incorrectly returns False. It seems like the check for `is_new_widget_value` shouldn't be part of that method. The method implementation should have been a conservative simplification of the old one that stripped out the initial value handling and separated this check from setting the value of a new widget, so I can't see why the script would have worked in 0.88, but also the current behavior is obviously incorrect. Removing the second part of the check would make it match the obvious notion that the frontend should have its value overridden whenever the value is set in session state, and trying out this change locally appears to fix the problem.

In terms of the font choices and such, you should be able to change some of that via our theming functionality, though it may not be as fine-grained as you are hoping for.

Best,
Randy

Kareem_Rasheed_babat · October 7, 2021, 4:10am

This is exciting, am growing with streamlit, let’s go guys.

system · October 7, 2022, 4:10am

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Version 0.84.0 📣 Official Announcements release-notes	10	3069	August 15, 2022
Problems with the new widget behaviour under streamlit 0.89.0 🎈 Using Streamlit session-state	3	473	October 6, 2022
Bug causing widget reset 🎈 Using Streamlit	10	1449	February 10, 2024
Mini-tutorial: Initializing widget values and getting them to stick without double presses 💬 Show the Community! session-state	6	2434	January 23, 2024
Session state key-widget association bug 🎈 Using Streamlit	3	461	August 10, 2021

Version 1.0.0

Related Topics

Hello there 👋🏻

Cookie settings

Strictly necessary cookies

Performance cookies

Functional cookies

Targeting cookies