Deprecated stuff.

[mxav1111]

Question

Hi Team
I have been using flet for over a year.. somewhere around 0.23 .. 0.24.. 0.25..0.26 and now 0.27.4.
After upgrading code won't run and multiple issues have come up (and i am still worried many more will show up..)

Deprecated issues ...
import failed for :- UserControl, and then for theme.
file_picker changed to use file_picker.pick_files (w/o await).

I am wondering what is the best way to identify if something is deprecated and sitting in there when Flet doesn't report it..

Can we have some kind of script to run , especially before the upgrade to ensure we don't end up with dead or wounded application post upgrade?

Admittedly I am taking lots of help from AI to speed up writing the code and it quietly advices the stuff that probably is obsolete.

So if there's some kind of script that can be regularly executed to look for deprecation (and specifically before the upgrade) on the code directory structure, it would be very helpful. I think this is a necessity as upgrades are rapid although very useful.

Any suggestions how do we deal with this?

Code sample

No response

Error message

No response

------------------------------------------------------

• I have searched for answers to my question both in the issues and in previous discussions.

[ndonkoHenri]

Deprecate stuffs are removed after three releases (for ex: if y is deprecated in 0.27.0, it will be removed in 0.30.0).
We mention in the the release announcements, when deprecating/removing: https://flet.dev/blog/tags/releases

Concerning UserControl, read this for migration: https://flet.dev/docs/getting-started/custom-controls

[mxav1111]

Thank you @ndonkoHenri for the response. I corrected those problems.
Bigger problem is identifying the code on regular basis (even when we are not upgrading) as lots of advises are provided by AI. At least in my case and this is going to increase.

Would it be possible to maintain simple grep based script instead of release notes or in addition to release notes? We can run such script on code structure to scan and it will extract deprecation call, version deprecated and the URL where it has alternative documented.

While I am really in bad shape and it is likely because of my dependence on AI is to blame :-(. However, script based approach (in addition/replacement to release notes can eliminate these headaches as we simply cron it to run every day.

Looking forward to some kind of automation that can help resolve this today and for future..
Flet is a great tool and is extremely helpful platform.

Thanks for your help @ndonkoHenri and the flet team🙏.

[robinchiyo]

Yes, this is a very useful suggestion. I also use DeepSeek AI to write code extensively.