Am 28.02.2018 um 16:47 schrieb Robin Becker:
> I upgraded pyinstaller using the very latest pip and now the version
> of pyinstaller at least is 3.3.1. I don't actually know how to check
> the validity of the installed code or the binary stubs.
The current archives are PyPI are PGP/GnuPG-signed,
On 28/02/2018 16:25, Hartmut Goebel wrote:
Am 28.02.2018 um 16:47 schrieb Robin Becker:
I upgraded pyinstaller using the very latest pip and now the version
of pyinstaller at least is 3.3.1. I don't actually know how to check
the validity of the installed code or the binary stubs.
The current
Am 28.02.2018 um 16:47 schrieb Robin Becker:
> I upgraded pyinstaller using the very latest pip and now the version
> of pyinstaller at least is 3.3.1. I don't actually know how to check
> the validity of the installed code or the binary stubs.
The current archives are PyPI are PGP/GnuPG-signed,
On 28/02/2018 11:46, alister via Python-list wrote:
On Wed, 28 Feb 2018 09:53:09 +, Robin Becker wrote:
I see this has happened to others in the past. I'm using 32 bit python
2.7.10 with py2exe 3.3 on windows 7. The exes work fine,
but when I try to download into windows 10 I'm getting the
On Wed, 28 Feb 2018 09:53:09 +, Robin Becker wrote:
> I see this has happened to others in the past. I'm using 32 bit python
> 2.7.10 with py2exe 3.3 on windows 7. The exes work fine,
> but when I try to download into windows 10 I'm getting the exes
> immediately removed as malware.
>
> Is th
