I think it's definitely the antivirus. There was a time, yesterday, that it 
was not active and all my distributes worked fine (both --onefile or 
--onedir). Today it's pretty bad and just checked the antivirus is on. It's 
IT guys who handle this so don't know what to do . However, I thought the 
--onedir version would not trigger the antivirus but it does anyway.

On Tuesday, September 20, 2016 at 3:07:30 AM UTC-3, Steve Barnes wrote:
>
>
>
> On 19/09/2016 21:23, maurice wrote: 
> > So all this time is due to unpacking? Also sometimes it's much quicker 
> > (like 10s) and in some other cases it exceeds 1 minute. 
> > 
>
> If you have recently run the packed code, i.e. last few minutes, your OS 
> cashing may well go - you just deleted those files and need them back so 
> here you go. Also some anti-virus software can cause a huge variability 
> - the first time that you run it will scan the entire packed executable 
> before allowing it to run, scan the files it writes as it writes them 
> and in some cases scan them again as they are read but once it has done 
> so may just verify that it is the same unchanged file. Also any dynamic 
> load libraries are loaded into RAM at the first run and don't 
> necessarily remove themselves as soon as you exit so a second run 
> shortly after the first can be faster from that as well. 
>
> -- 
> Steve (Gadget) Barnes 
> Any opinions in this message are my personal opinions and do not reflect 
> those of my employer. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Reply via email to