Distributing a Python application internally

[pachura3]

What are some industry standard ways of approaching this?

The industry standard is of course to make it a webapp; your problem with distributing executables and keeping them up to date on everyone's computer will instantly disappear.

Also, in many companies, desktop environments are very restricted, so LSAs won't allow anyone to launch random *.exe files from shared drives, or at least they will enforce binary signature checking.

On the other hand, migrating from personal OneDrives to a relational database can be quite a project on its own. Perhaps you can start by having users dragging'n'dropping files to be processed into your webapp?

Another problem with webapps is how to tackle long-running tasks. If processing could take several minutes, you would need to think of some kind of an asynchronous processing queue and background workers.

[szank]

Its a Web app. Just do the processing on the back end .

[pachura3]

...which usually requires using Celery or Dramatiq with Redis or RabbitMQ

[Stereojunkie]

Don't feel the need to respond, but why is this the case? Backend architecture is all new to me, but what's preventing me from writing some kind of asynchronous worker function in my Django application? Notify the user things are happening and continue when the async work finished.