OK, stop the presses. Or, rather, refresh your browser, I guess.
In a 'what the !@#$ am I doing'-moment (I don't get those often) I uninstalled
everything and went gardening. But it was raining so I installed everything
again, this time using pip for wxpython. Lo and behond, this time it did not
OK, stop the presses. Or, rather, refresh your browser, I guess.
In a 'what the !@$$ am I doing'-moment (I don't get those often) I uninstalled
everything and went gardening. But it was raining so I installed everything
again, this time using pip for wxpython. Lo and behond, this time it did not
Oh, another thing. I installed WX via a windows installer that I found (can't
find the link again, but fairly certain it was this one:
https://sourceforge.net/projects/wxpython/ (*)), without giving it much thought
(yesyes bad mistake).
Since I get wx runtime errors, I'm assuming I have the wro
Really, no-one?
OK, more purging then. I ~think~ I need said missing component because the
script gets the system date (to run once on a Friday, in automatic mode). But
I've never used it in automatic mode (since I came to my senses about having an
infinite looping script in my autoexec.bat, do
Well that escalated quickly :).
So, no-one can tell me which component to pip to get rid of "missing
['_sysconfigdata']" error?
--
https://mail.python.org/mailman/listinfo/python-list
Matthew Lemon wrote:
> If the OP was able to take the time to familiarise himself with the
> technologies, rather than bemoan the difficulty of deploying a ten year old
> code-base without mininal effort, he might have some success. Code rot is an
> issue after weeks sometimes, never mind ten ye
Grant Edwards wrote:
...
> 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.
i looked at the one and stopped at that because
alas, i have no Windows or MacOS machines to
genera
MRAB wrote:
> On 2019-01-09 14:56, songbird wrote:
>> Chris Angelico wrote:
>> ...
>>> You want it to work with minimal effort? Then forget about py2exe and
>>> just distribute your .py files. WAY easier.
>>
>>which then forces the work onto every other
>> person who might install it, if they
Chris Angelico wrote:
...
> This is true - but on the flip side, it's a bit unfair to say "blah
> blah Python sucks because py2exe is hard". That's not Python's fault.
> You have an additional requirement ("support people who can't install
> Python"), and that's going to have extra hassles. LOTS of
On 2019-01-09, Chris Angelico wrote:
> On Thu, Jan 10, 2019 at 2:37 AM Grant Edwards
> wrote:
>
>> > How many platforms support .exe files that were compiled for Windows?
>>
>> None.
>>
>> But when your requirement is to support Windows users who are not
>> capable of installing Python, WxWindow
If the OP was able to take the time to familiarise himself with the
technologies, rather than bemoan the difficulty of deploying a ten year old
code-base without mininal effort, he might have some success. Code rot is an
issue after weeks sometimes, never mind ten years, and Python deployment is
On Thu, Jan 10, 2019 at 2:37 AM Grant Edwards wrote:
>
> On 2019-01-09, MRAB wrote:
>
> > .py files work on any platform that supports Python: Windows, Linux,
> > MacOs, ...
>
> Only after python has been installed along with any other required
> libraries.
>
> > How many platforms support .exe f
On 2019-01-09, MRAB wrote:
> .py files work on any platform that supports Python: Windows, Linux,
> MacOs, ...
Only after python has been installed along with any other required
libraries.
> How many platforms support .exe files that were compiled for Windows?
None.
But when your requirement
On 2019-01-09 14:56, songbird wrote:
Chris Angelico wrote:
...
You want it to work with minimal effort? Then forget about py2exe and
just distribute your .py files. WAY easier.
which then forces the work onto every other
person who might install it, if they are on a
different architecture o
Chris Angelico wrote:
...
> You want it to work with minimal effort? Then forget about py2exe and
> just distribute your .py files. WAY easier.
which then forces the work onto every other
person who might install it, if they are on a
different architecture or system it even gets
worse if you add
On 2019-01-09, Chris Angelico wrote:
> On Thu, Jan 10, 2019 at 12:46 AM 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 a
On Thu, Jan 10, 2019 at 12:46 AM 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
d to update the script,
> >so needed to recompile the EXE, and now it no longer compiles/works. It
> >was fine on Windows7 (I'm not specifically stating that the problem is
> >with windows10 - I simply don't remember all the hoops I jumped through
> >on my p
ith windows10 - I simply don't remember all the hoops I jumped through
>on my previous machine).
>
>Here is the compile error:
>The following modules appear to be missing
>['_sysconfigdata']
>
>And here is the runtime error:
>Traceback (most recent call la
(I'm not specifically stating that the problem is with windows10 -
I simply don't remember all the hoops I jumped through on my previous machine).
Here is the compile error:
The following modules appear to be missing
['_sysconfigdata']
And here is the runtime error:
Traceba
20 matches
Mail list logo
