Hypothetical scenario: Python standalone executable for future machine compatibility [closed]
I have used Python (version 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 16:07:46) [MSC v.1900 32 bit (Intel)] on win32) and pyinstaller (version 3.3.1) to build a standalone executable for only windows OS usage. This executable runs perfectly every time it is called.
I want this application to be available and usable for future changes and releases of windows. Is it possible/likely that in future releases that this executable will stop functioning? If so, what exactly would be the cause?
python windows executable pyinstaller
closed as too broad by DavidG, g.d.d.c, Gert Arnold, gnat, sideshowbarker Nov 17 at 22:23
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I have used Python (version 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 16:07:46) [MSC v.1900 32 bit (Intel)] on win32) and pyinstaller (version 3.3.1) to build a standalone executable for only windows OS usage. This executable runs perfectly every time it is called.
I want this application to be available and usable for future changes and releases of windows. Is it possible/likely that in future releases that this executable will stop functioning? If so, what exactly would be the cause?
python windows executable pyinstaller
closed as too broad by DavidG, g.d.d.c, Gert Arnold, gnat, sideshowbarker Nov 17 at 22:23
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I have used Python (version 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 16:07:46) [MSC v.1900 32 bit (Intel)] on win32) and pyinstaller (version 3.3.1) to build a standalone executable for only windows OS usage. This executable runs perfectly every time it is called.
I want this application to be available and usable for future changes and releases of windows. Is it possible/likely that in future releases that this executable will stop functioning? If so, what exactly would be the cause?
python windows executable pyinstaller
I have used Python (version 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 16:07:46) [MSC v.1900 32 bit (Intel)] on win32) and pyinstaller (version 3.3.1) to build a standalone executable for only windows OS usage. This executable runs perfectly every time it is called.
I want this application to be available and usable for future changes and releases of windows. Is it possible/likely that in future releases that this executable will stop functioning? If so, what exactly would be the cause?
python windows executable pyinstaller
python windows executable pyinstaller
asked Nov 12 at 16:42
Nate Benton
1134
1134
closed as too broad by DavidG, g.d.d.c, Gert Arnold, gnat, sideshowbarker Nov 17 at 22:23
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by DavidG, g.d.d.c, Gert Arnold, gnat, sideshowbarker Nov 17 at 22:23
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There's never going to be any firm guarantee that software built for an older operating system continues to work on any conceivable future operating system. That's analogous to asking "Can you guarantee that every car everywhere will always support my carburetor?"
That's demonstrably false, but also patently absurd to ponder. No one can tell you what will or won't change in future operating systems, or what might introduce a binary incompatibility for a script compiled in the past.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There's never going to be any firm guarantee that software built for an older operating system continues to work on any conceivable future operating system. That's analogous to asking "Can you guarantee that every car everywhere will always support my carburetor?"
That's demonstrably false, but also patently absurd to ponder. No one can tell you what will or won't change in future operating systems, or what might introduce a binary incompatibility for a script compiled in the past.
add a comment |
There's never going to be any firm guarantee that software built for an older operating system continues to work on any conceivable future operating system. That's analogous to asking "Can you guarantee that every car everywhere will always support my carburetor?"
That's demonstrably false, but also patently absurd to ponder. No one can tell you what will or won't change in future operating systems, or what might introduce a binary incompatibility for a script compiled in the past.
add a comment |
There's never going to be any firm guarantee that software built for an older operating system continues to work on any conceivable future operating system. That's analogous to asking "Can you guarantee that every car everywhere will always support my carburetor?"
That's demonstrably false, but also patently absurd to ponder. No one can tell you what will or won't change in future operating systems, or what might introduce a binary incompatibility for a script compiled in the past.
There's never going to be any firm guarantee that software built for an older operating system continues to work on any conceivable future operating system. That's analogous to asking "Can you guarantee that every car everywhere will always support my carburetor?"
That's demonstrably false, but also patently absurd to ponder. No one can tell you what will or won't change in future operating systems, or what might introduce a binary incompatibility for a script compiled in the past.
answered Nov 12 at 17:47
g.d.d.c
34k77194
34k77194
add a comment |
add a comment |