On 4/10/2007 5:17 PM, mathieu wrote: > I have recently started using PyInstaller and I am trying to > evaluate if it can do what I am looking for. Right now my application > is not bundle at all, all *.pyc are distributed. This is a tedious > work to do, the nice thing though is that I can change only one file > (let say to change a configuration file) and that's it ! No need for > the customer to redownload the whole application.
Well, the idea of PyInstaller is putting everything together... so that pretty much is the opposite of the concept of "updating a single file" that you're listing as a feature. Two comments though: 1) Even if you bundle everything with PyInstaller, you can still cut the download time down by allowing your users to rsync. With rsync, only the differences are transmitted (the moral equivalent of the single .pyc file). 2) PyInstaller does not prevent import of external .pyc files: they just happen "later" in the import chain than the files bundled with PyInstaller itself. But if you inserto any directory of your choice in sys.path[0] at runtime, and put updated .pyc files there, your application will import them and ignore anything bundled within the executable. HTH! -- Giovanni Bajo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
