<transcript><audio_225>see why and 20 of July we decided in this Cy to tentatively accept pep 703 which means that we are going to uh you know accept it with some caveats but as you can see it took us a long time to decide that we wanted to follow this</transcript><transcript><audio_226>this path so why is this a challenge why what what is different difficult with thing well the first thing is that uh even if this works and it's a fantastic work on engineering is quite complicated this complicates see python quite a lot</transcript><transcript><audio_227>and this I'm talking about maintainance here so so this makes this basically makes python very difficult to maintain which means that it's going to be harder for us to fix backs harder for us to you know like like uh Sol add new features and ens sure that it works with</transcript><transcript><audio_228>everything right so so it means that maintaining python will be harder for the people that we're doing that and then it has some compatibility problems because C extensions like numai or Panda something think like that sap they may not be compatible with the guild because you know right now they are thinking</transcript><transcript><audio_229>that is a massive lock uh but when the lock is not there then now what happens there's also a performance implication okay so so you can have parallelism and that is quite nice performance you know now you can have like multiple threads running python yeah but like now what what happens with like single thread</transcript><transcript><audio_230>python like that when the Gil doesn't matter well maybe it's a bit slower and maybe uh you know some of the things that no Gil needs is are incompatible with the faster SE python team optimizations that we have right now</transcript><transcript><audio_231>right python 312 and 311 and much faster than 39 and 310 due to the work of the faster python team so so noil may not be the best fit for that and then packaging is it can be quite complicated because if the nogil is uh binary incompatible it means that you need to generate</transcript><transcript><audio_232>binary wheels for Gil and nogil which mean that every single package needs to publish twice the same number of artifacts which will complicate and and will complicate testing and and packaging quite a lot so we are trying to figure out how to solve all of these</transcript> see why and 20 of July we decided in this Cy to tentatively accept pep 703 which means that we are going to uh you know accept it with some caveats but as you can see it took us a long time to decide that we wanted to follow this this path so why is this a challenge why what what is different difficult with thing well the first thing is that uh even if this works and it's a fantastic work on engineering is quite complicated this complicates see python quite a lot and this I'm talking about maintainance here so so this makes this basically makes python very difficult to maintain which means that it's going to be harder for us to fix backs harder for us to you know like like uh Sol add new features and ens sure that it works with everything right so so it means that maintaining python will be harder for the people that we're doing that and then it has some compatibility problems because C extensions like numai or Panda something think like that sap they may not be compatible with the guild because you know right now they are thinking that is a massive lock uh but when the lock is not there then now what happens there's also a performance implication okay so so you can have parallelism and that is quite nice performance you know now you can have like multiple threads running python yeah but like now what what happens with like single thread python like that when the Gil doesn't matter well maybe it's a bit slower and maybe uh you know some of the things that no Gil needs is are incompatible with the faster SE python team optimizations that we have right now right python 312 and 311 and much faster than 39 and 310 due to the work of the faster python team so so noil may not be the best fit for that and then packaging is it can be quite complicated because if the nogil is uh binary incompatible it means that you need to generate binary wheels for Gil and nogil which mean that every single package needs to publish twice the same number of artifacts which will complicate and and will complicate testing and and packaging quite a lot so we are trying to figure out how to solve all of these
{"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"}}