2

Say I have developed an application Awesome and deployed it onto a user machine with an artefact made with PyInstaller. Let's just consider the Mac OS X artefact for now, Awesome.app.

During the installation process, Awesome.app is registered to open files of type *.awesome and to handle URLs of the form awesome://* (i.e. handle the custom protocol awesome).

The user runs an instance of Awesome.app. For the sakes of argument let's say it has process id 1234. Then, the user opens a file foo.awesome.

How can I ensure that this open event is handled by the already-running Awesome process 1234? What code path actually taken for this to happen within the Python application?

If the answer is platform-specific I'd still like to hear about each of Windows, Mac OS X and Ubuntu.

fatuhoku
  • 4,815
  • 3
  • 30
  • 70
  • I found that the best answer to doing this on Mac can be found here: http://stackoverflow.com/questions/471581/how-to-map-a-custom-protocol-to-an-application-on-the-mac – fatuhoku Oct 17 '13 at 10:18
  • This of course does not answer the question. I'm just confused about what code path is taken to communicate with the running process that it needs to open a file. – fatuhoku Oct 17 '13 at 10:55
  • Did you found out the answer. – Durgaprasad Jul 07 '17 at 07:36

0 Answers0