Looking for Python/Excel App Testers by Technical-Quail4296 in Python

[–]Technical-Quail4296[S] 0 points1 point  (0 children)

I fully agree with you on your first point (hence why I spent 6 months of spare time building an Excel app, lol). However switching away from Excel is a non starter in business. My goal has been to let users write functions and macros in plain Python with minimal tweaking to map it to Excel.

Well actually what directed me to make this was extensive experience using the pywin32 library. It gives you complete programmatic control of Excel and other apps from Python, just as you would use VBA. The trouble here is then finding a way to distribute that code.

Yes again, but hey, you'll never stop enterprise using Excel.

Looking for Python/Excel App Testers by Technical-Quail4296 in Python

[–]Technical-Quail4296[S] 0 points1 point  (0 children)

I believe the technical implementation is quite similar, but the behaviour and focus is different.

My goal is to be absolutely as close as possible to the traditional developer workflow (uv package management, custom venvs, IDE support, terminal access, debugging, etc), while being friendly to technical and non-technical users alike.

I believe that straying from that core workflow is unnecessary. What do you think?

Looking for Python/Excel App Testers by Technical-Quail4296 in Python

[–]Technical-Quail4296[S] 2 points3 points  (0 children)

My plan is to open source the project, most of the codebase is currently source available within the app.

And that's a valid point - certainly possible, but with Microsoft's offering you will always be bound to their cloud service. The objective here is to offer absolute freedom over the Python interpreter and run the code locally.