On 2019-01-09, Chris Angelico <ros...@gmail.com> wrote:
> On Thu, Jan 10, 2019 at 12:46 AM <dude.ji...@gmail.com> wrote:
>> step 5, pyinstaller, is yet another hurdle I hope to avoid. It worked with
>> py2exe, and it should still work with py2exe (within the efforts I'm
>> prepared to put into this). Of course py2exe might be ancient and horrible
>> and a bunch of other things that pyinstaller is not (I woulnd't know either
>> way), but, to be honest, as well a tad cocky, I am not interested nor
>> prepared to find out. Sorry about that, but hopefully one can understand.
>> I'm not trying to 'get back into Python' , I just want something from the
>> past back working again with minimal effort.
>>
>
> You want it to work with minimal effort? Then forget about py2exe and
> just distribute your .py files. WAY easier.
It may be easier, but it may not be feasible. That depends on what
dependencies are involved and whether your target audience is capable
of installing Python and those dependencies. Distributing .py files
to my Windows customers is absolutely out of the question. There's no
way I can expect them to install Python and whatever other
dependenceis are required by my applications.
That said, I've recently switched from py2exe to cx_freeze. However,
even that isn't simple enough for my users, and I bundle the output
from those with Inno Setup.
--
Grant Edwards grant.b.edwards Yow! I'll show you MY
at telex number if you show me
gmail.com YOURS ...
--
https://mail.python.org/mailman/listinfo/python-list
