We wrote the OpenAI Wanderlust app in pure Python using Solara

Well for itineraries, given that its training data gets cut off at some point, I’d also be worried about it recommending places that are no longer open.

Note that I’m building an app for customers and attempting to build a brand that can be trusted - whereas in your case gpt 4 is probably ideal given you know it’s caveats and can check the important stuff.

Also, they literally just demoed something similar as this project as part of their recent keynote on new openai stuff. The demo featured focused on their new assistant api.

I've actually grilled chat gpt a bit on geographic information on a few occasions. It's not perfect but surprisingly good. It obviously extracts a lot of that from things like wikipedia.

You can actually ask it to answer in geojson format, paste it in geojson.io and end up with a usable map. It seems to know about a lot of landmarks; including coordinates. For smaller venues, the coordinates are not super accurate.

You can also ask it to provide geojson for the boundingbox of a city or area. I even asked it to pretend to be an in car navigation system and provide me with directions to an address. It half succeeded in listing correct streets but messing up right and left. With the latest chatgpt it just asks bing.

For anyone else that is interested in this question: I've tried a whole bunch of the TTS services and found that Microsoft and AWS are the best of the standard providers IMHO and these are services that tend to have startup credits available so I use a mix of these two - I try to never rely on just one provider. I've met with the Eleven Labs folks and some of their demo's of the V2 stuff that's coming are really amazing but latency and pricing might rule them out as an option for the time being.

because it's not like human travel agents don't exist today, just like human drivers exist today. Does having an AI book the tickets for you meaningfully change the things for you, the customer?

I ask it to write it in small chuncks but in the same context. I sometimes have to remind it to refer back to decisions we made earlier.

* Solara will not continuously re-execute your script as Streamlit does.

* Solara will re-execute components instead, only what needs to. * State in Solara is separate from the UI components, unlike streamlit, where they are strongly linked.

* State can be on the application level (global) for simplicity or on the component level (local) for creating reusable components.

* Solara should not block the render loop. Long-running functions should be executed in a thread using use_thread.