# Handling incompatibilities with App Store review processes

**URL:** <https://discuss.python.org/t/handling-incompatibilities-with-app-store-review-processes/56011>\
**Category:** Core Development\
**Created:** [June 17, 2024, 10:37pm UTC](https://discuss.python.org/t/handling-incompatibilities-with-app-store-review-processes/56011 "2024-06-17T22:37:22Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![ncoghlan](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ncoghlan/32/14266_2.png) [@ncoghlan](https://discuss.python.org/u/ncoghlan)\
**Post date:** [June 18, 2024, 7:58am UTC](https://discuss.python.org/t/handling-incompatibilities-with-app-store-review-processes/56011/12 "2024-06-18T07:58:00Z")

</div>

Reading the [original issue](https://github.com/python/cpython/issues/104139) that added `itms-services` support to url splitting and joining, it does make me wonder if it would be worth changing `urllib` to read the initial setup of its module level attributes from a JSON config file bundled with the standard library rather than hardcoding its knowledge of all the relevant schemes.

Then the bundled app generators could just drop `itms-services` from that config file rather than having to patch `urllib.py` directly.

As a more general case though, I think it does make sense to view this as equivalent to Linux distro patching (even with the URL schema config file idea, the bundled app generators would still need to modify the config file).

---

_[View the full topic](https://discuss.python.org/t/handling-incompatibilities-with-app-store-review-processes/56011)._