<transcript><audio_197>annotations at run time so to validate for instance that you are actually passing a float even if uh you know you receive it from some Json and an example of this is pantic you know it will validate it only when python runs so this examp this these things uh only</transcript><transcript><audio_198>happen when python runs uh so this these were introducing in different peps originally when we introduced the you know all the annotations in pep 4 48 before we only were thinking about the static usage of these annotations so all the feature sets and all the ideas were</transcript><transcript><audio_199>introduced uh with this in mind um then uh we realized that there were some problems with this we will see which ones in a second uh and then it was this pep 563 that introduced this idea of having from future import annotations to treat all annotations as strings which</transcript><transcript><audio_200>fixes the problems I will tell you in a second which problems but turns out that this was still not working for all cases because people that are using annotations dynamically still needed the actual objects there right for example</transcript><transcript><audio_201>pantic so recently we have another pep which was recently um you know accepted by the steing council uh which basically introduced a mechanism for allowing this tricky situations to work so so quite a lot of um different uh ways to approach</transcript> annotations at run time so to validate for instance that you are actually passing a float even if uh you know you receive it from some Json and an example of this is pantic you know it will validate it only when python runs so this examp this these things uh only happen when python runs uh so this these were introducing in different peps originally when we introduced the you know all the annotations in pep 4 48 before we only were thinking about the static usage of these annotations so all the feature sets and all the ideas were introduced uh with this in mind um then uh we realized that there were some problems with this we will see which ones in a second uh and then it was this pep 563 that introduced this idea of having from future import annotations to treat all annotations as strings which fixes the problems I will tell you in a second which problems but turns out that this was still not working for all cases because people that are using annotations dynamically still needed the actual objects there right for example pantic so recently we have another pep which was recently um you know accepted by the steing council uh which basically introduced a mechanism for allowing this tricky situations to work so so quite a lot of um different uh ways to approach
{"source": "grass-yt-cc-by.0C4eKA5DXFs|shard_10016_22|create_multimodal_data.extract_yt_and_generate_transcripts.62|shard_10016|create_multimodal_data.generate_captions.42|shard_10016|create_multimodal_data.generate_captions.55", "params": {"id": "0C4eKA5DXFs", "channel_id": "UCHLnNgRnfGYDzPCCH8qGbQw", "duration": 4151, "view_count": 107, "age_limit": 0, "like_count": 3, "channel_follower_count": 6170, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@PyConTaiwanVideo", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10016/0C4eKA5DXFs.tar.gz"}}