Self.button2 = tk.Button(self.rightframeheader, text='Clear', command=self.clear, width=10) Self.button1 = tk.Button(self.rightframeheader, text='Import CSV', command=self.import_csv, width=10) Self.rightframeheader = tk.Frame(self.rightframe, background='white') Self.leftframe = tk.Frame(self.main, background='white') Self.rightframe = tk.Frame(self.main, background='white') Self.main = tk.Frame(master, background='white') Now obviously this is a big problem, especially if you have several large libraries lying around which are not actually being used.įrom tkinter.filedialog import askopenfilename, asksaveasfileįrom _tkagg import FigureCanvasTkAggįrom llections import PatchCollection Regardless of whether they are actually needed, or not. When we normally use Pyinstaller to bundle our applications, it ends up including ALL of the libraries that we have installed. Now you might have already put two-and-two together and realized the problem here. Running this on my old device might have given me double the above amount.

And this is on a relatively new Python installation (3-4 months old). Reason for discarding try/except because, if you generate console exe then try/except will unnecessarily generates warnings, so to completely avoid warnings also, this can be a good check.That was quite a long list right? I don’t even recognize half of those libraries (they were installed as dependencies). More elegant way to close the splash screen if '_PYIBoot_SPLASH' in os.environ and _spec('pyi_splash'): try:Īnd put this splash screen close code with in try block as it is needed only for package execution,Īnd can just pass on exception and proceed at the time of development runs. Adding -splash splashfile.png gave me high pink color shades on splash screen, so I used JPG image with some colored background and it worked very well.Īnother update we need to close splash, within our project code in any suitable place feasible for us, else splash screen remains on top of UI until application itself is closed.

Python pyinstaller