Randy Zwitch

Thanks for reporting... @hansthen, would you have any insight here about why this might happen? The comment listed references adding `:use-global-leaflet="true"`, but not being a leaflet expert I'm not sure...

Closing, as it doesn't seem like it's happening enough to make numerous people have issues. If this arises again, please post a reproducible example and we'll re-open

Hi @wrenchInTheWorks - When you say "build up", you're talking about the values being outside of the -180, 180 bounds?

It appears this is the default behavior in leaflet (the library that Folium wraps, that we wrap for this package 😅): https://stackoverflow.com/questions/18063278/leaflet-getbounds-returning-longitudes-greater-than-180 @blackary, I'm not sure I even understand why...

No bother at all, it's definitely a weird default!

Turns out, this is the same as #145

Looks like the community isn't ready yet, will keep open and try next week

Looks like the problem is that greenlet uses 3.0.3, when it needs to be 3.1 (which specifically supports python 3.13). But as far as I can tell, we don't require...

Merging master in fixed the greenlet version issue*, but it's still trying to compile Arrow from source *could be coincidental, but fixed nonetheless

Have you tried to do this without including this code inside a function? ```python def search_area(): m = folium.Map() Draw().add_to(m) Geocoder().add_to(m) st_folium(m, height=350, use_container_width=True) ``` Because of the Streamlit execution...