> I agree in principle, but one thing you get with setup.cfg which seems harder to > achieve with MSI is the use of Python to do things at installation time. For > example, with setup.cfg hooks, you can use ctypes to make Windows API calls at > installation time to decide where to put things. While this same flexibility > exists in the MSI format (with custom actions and so forth) it's not as readily > accessible to someone who wants to use Python to code this type of installation > logic. Again, that's a bdist_msi implementation issue. It could generate custom actions that run the "proper" setup.cfg hooks (I presume - I have no idea what a setup.cfg hook actually is). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4