*#How to use setup.py file with py2exe:*
**
python daniesetup.py py2exe --bundle 1
*#Also the data files have to taken care off in the options* list
*#Here is a sample setup.py:*
*#*
from distutils.core import setup
import py2exe
import sys
# n
> the method involves editing python26.dll in order to remove
> dependency references and then dropping msvcr90.dll in the same
> directory as the py2exe produced executable.
Clever idea Waldemar, thanks for that, but for the moment, using the
dll as a win32 assembly (ie. with a manifest file, as
Waldemar,
Thank your for sharing your technique - works great with 32-bit Python
2.6.4.
Has anyone tried this with a 64-bit version of Python?
Malcolm
--
http://mail.python.org/mailman/listinfo/python-list
On Dec 30, 10:05 am, kakarukeys wrote:
> I tried on a fresh XP on VM. I moved all dlls in C:\WINDOWS\WinSxS
> which are in the file handles shown by Process Explorer including the
> 3 CRT dlls to the my dist folder and the two subfolders suggested
> byhttp://wiki.wxpython.org/py2exe. It didn't wo
Hi all,
#use py2exe properly to create a single distributable exe
#setup.py- create a single exe that runs all boxex
from distutils.core import setup
import py2exe
import sys
# no arguments
if len(sys.argv) == 1:
sys.argv.append("py2exe")
# creates a standalone .exe file, no zip files
setup(
I tried on a fresh XP on VM. I moved all dlls in C:\WINDOWS\WinSxS
which are in the file handles shown by Process Explorer including the
3 CRT dlls to the my dist folder and the two subfolders suggested by
http://wiki.wxpython.org/py2exe. It didn't work out. My app couldn't
start. Windows XP gave a
Jonathan Hartley writes:
> I guess I really need an installer. Oh well.
This need not be that much of a hurdle. Several solutions exist such
as Inno Setup (my personal preference), NSIS, etc... which are not
hard to create a solid installer with. I suspect your end users will
appreciate it too
On 29/12/2009 18:31, pyt...@bdurham.com wrote:
Jonathan,
I'm going to try to run vcredist_x86.exe automatically (as opposed to
asking my users to download and run it manually). I don't currently
have any installer, so I'm going to run vcredist_x86.exe on my
application start-up. Some logic like
Jonathan,
I'm going to try to run vcredist_x86.exe automatically (as opposed to
asking my users to download and run it manually). I don't currently
have any installer, so I'm going to run vcredist_x86.exe on my
application start-up. Some logic like this seems to do this trick:
if platform.sy
>> However, this takes a few seconds to run. Is there a sensible way for
>> me to only run this if the required DLL is not already installed? How
>> should I be detecting that?
Look at windows\winsxs\
>> Also: Will this work on 64 bit machines? Or do I not need to worry
>> about that?
If you shi
On Dec 29, 2:24 pm, Jonathan Hartley wrote:
> On Dec 27, 1:51 pm, pyt...@bdurham.com wrote:
>
>
>
> > Hi Martin,
>
> > > You'll need to include Microsoft.VC90.CRT.manifest and msvcr90.dll.
>
> > Thank you for your answers. From my research and testing on this topic:
>
> > 1. Can I safely place the
On Dec 27, 1:51 pm, pyt...@bdurham.com wrote:
> Hi Martin,
>
> > You'll need to include Microsoft.VC90.CRT.manifest and msvcr90.dll.
>
> Thank you for your answers. From my research and testing on this topic:
>
> 1. Can I safely place these 2 files in the same folder as my Py2exe
> generated EXE fi
On 27/12/2009 05:18, Stephen Hansen wrote:
Jonathan Hartley mailto:tart...@tartley.com>>
writes:
These
are non-technical users, so I'd rather send them a single executable
that 'just works',
[break]
rather than asking them to install Python and then
coach them through
> Thank you for your answers. From my research and testing on this topic:
Unfortunately, I can't answer these questions for py2exe. In principle,
it would hope that it is possible to include the DLLs *in* the
executable, if the py2exe mode is used where it includes all DLLs.
Regards,
Martin
--
h
Hi Martin,
> You'll need to include Microsoft.VC90.CRT.manifest and msvcr90.dll.
Thank you for your answers. From my research and testing on this topic:
1. Can I safely place these 2 files in the same folder as my Py2exe
generated EXE file or do I need to place the MSVCR90.DLL file in a
speciall
> Does anyone have any recommendations on which version of the
> MSVC?90.DLL's need to be distributed with a Python 2.6.4 PY2EXE (0.6.9)
> based executable?
You'll need to include Microsoft.VC90.CRT.manifest and msvcr90.dll.
Regards,
Martin
--
http://mail.python.org/mailman/listinfo/python-list
> FYI, my experience is that an entire manifest must be distributed. As
> the manifest in question actually lists 3 DLLs, IIUC, you must ship all
> 4 files - the 3 DLLs and the manifest, even if only one of the DLLs is
> actually used.
You don't actually need to include all three DLLs. Just inclu
Jonathan Hartley writes:
> These
are non-technical users, so I'd rather send them a single executable
> that 'just works',
[break]
rather than asking them to install Python and then
> coach them through running a script - they would HATE that as a
> solution.
>
Whoa... How can you go from
Jonathan Hartley writes:
> 2) About once a week the last couple of months I've had a friend phone
> to say 'can you write me a simple program to do X', where X is stuff
> like calling a web API to look up info for every postcode/zipcode in a
> database. This sort of thing is ideally suited to Pyt
On Dec 26, 3:14 pm, Ross Ridge wrote:
> Jonathan Hartley wrote:
>
> >Am I right to infer that if I want to distribute a py2exe'd
> >application legally, and have half a chance of it working on a non-
> >developer's machine, then I have to:
>
> >a) Ask my users to run the Visual C++ redistributab
Jonathan Hartley wrote:
>Am I right to infer that if I want to distribute a py2exe'd
>application legally, and have half a chance of it working on a non-
>developer's machine, then I have to:
>
>a) Ask my users to run the Visual C++ redistributable installer, as
>well as download my program. This
On Dec 21, 2:56 pm, Ross Ridge wrote:
> Jonathan Hartley wrote:
>
> >Many thanks for that, but my issue is that my programs work fine for
> >me on my computer - but then fail on other people's computers. I'd
> >very strongly prefer for my users to not have to install the MSVCR
> >redistributable
Jonathan Hartley wrote:
>Many thanks for that, but my issue is that my programs work fine for
>me on my computer - but then fail on other people's computers. I'd
>very strongly prefer for my users to not have to install the MSVCR
>redistributable installer as well as my program - it would be much
On Dec 17, 11:16 pm, Mark Hammond wrote:
> On 18/12/2009 7:44 AM, Ross Ridge wrote:
>
> > The "P" DLL is for C++ and so the original poster may not actually need
> > it. I'm pretty sure Python itself doesn't need it, and py2exe shouldn't
> > either, but wxPython, or more precisely wxWidgets, almo
On Dec 17, 8:39 pm, Christian Heimes wrote:
> Jonathan Hartley wrote:
> > Only this week I sent a py2exe-derived executable to someone else (a
> > non-developer) and it would not run on their WinXP machine ("'The
> > system cannot execute the specified program'") - my current favourite
> > hypothe
On 18/12/2009 7:44 AM, Ross Ridge wrote:
The "P" DLL is for C++ and so the original poster may not actually need
it. I'm pretty sure Python itself doesn't need it, and py2exe shouldn't
either, but wxPython, or more precisely wxWidgets, almost certainly does.
So in your case you'll probably need
Jonathan Hartley wrote:
>1) I don't understand why the OP's question doesn't deserve a literal
>answer ...
I gave what I thought was a simple, direct and literal answer.
>.. isn't one of those DLLs in the WinSxS directory derived from
>his MSVC install?
I have no idea. He might not even have
Jonathan Hartley wrote:
> Only this week I sent a py2exe-derived executable to someone else (a
> non-developer) and it would not run on their WinXP machine ("'The
> system cannot execute the specified program'") - my current favourite
> hypothesis is that my omission of this dll or something simila
On Dec 17, 5:36 pm, Ross Ridge wrote:
> wrote:
> >Does anyone have any recommendations on which version of the
> >MSVC?90.DLL's need to be distributed with a Python 2.6.4 PY2EXE (0.6.9)
> >based executable? (I assume I need just a matching pair of MSVCR90.DLL
> >and MSVCP90.DLL?)
>
> Either the o
wrote:
>Does anyone have any recommendations on which version of the
>MSVC?90.DLL's need to be distributed with a Python 2.6.4 PY2EXE (0.6.9)
>based executable? (I assume I need just a matching pair of MSVCR90.DLL
>and MSVCP90.DLL?)
Either the one the came with your copy Microsoft Visual C++ or P
Does anyone have any recommendations on which version of the
MSVC?90.DLL's need to be distributed with a Python 2.6.4 PY2EXE (0.6.9)
based executable? (I assume I need just a matching pair of MSVCR90.DLL
and MSVCP90.DLL?)
My understanding is that I need to match the version of the DLL's that
my ve
31 matches
Mail list logo
