Saint Germain wrote:
I'm currently trying more or less the same thing by combining buildout
with virtualenv and pip.
This doesn't seem like a sane thing to do.
These tools attempt to address the same problems in different ways.
Attempting to mash them together as it appears you have does nothi
2010/3/22 Chris Withers :
>> I'm currently trying more or less the same thing by combining buildout
>> with virtualenv and pip.
>
> This doesn't seem like a sane thing to do.
>
> These tools attempt to address the same problems in different ways.
> Attempting to mash them together as it appears yo
Gary Poster wrote:
Are these any docs on the new features on that branch? If so, where should I
look?
The user-visible part of the changes is in the z3c.recipe.scripts recipe
contained within the zc.buildout checkout, like zc.recipe.egg.
Sorry, you lost me there... I thought z3c.recipe.scri
Saint Germain wrote:
2010/3/22 Chris Withers :
I'm currently trying more or less the same thing by combining buildout
with virtualenv and pip.
This doesn't seem like a sane thing to do.
These tools attempt to address the same problems in different ways.
Attempting to mash them together as it
> The only reference to ErrorIcon was commented out by Martin a while
> ago. It was the icon attached to the Error Dialog you.
I'm not quite sure why I commented this out. See whether adding it back
fixes the problem.
The only reason I can see now is that py.ico isn't really an appropriate
error
> MSI (s) (40:E0) [18:35:46:882]: Note: 1: 1722 2: install_script 3:
> C:\Python26\\python.exe 4: C:\Python26\Scripts\foo-install-script.py
This means:
There is a problem with this Windows Installer package. A program run as
part of the setup did not finish as expected. Contact your support
per
2010/3/22 Chris Withers :
> Saint Germain wrote:
>>
>> 2010/3/22 Chris Withers :
>>
I'm currently trying more or less the same thing by combining buildout
with virtualenv and pip.
>>>
>>> This doesn't seem like a sane thing to do.
>>>
>>> These tools attempt to address the same problems i
On Mar 19, 2010, at 5:02 PM, Chris Withers wrote:
> Gary Poster wrote:
>> If you are a newbie, I strongly suggest sticking with the released versions.
>> What I have done has zero guarantee of Jim merging it.
>
> If he doesn't, how about a fork? ;-)
Rather not.
>> Moreover, the instructions
On Mar 22, 2010, at 5:21 AM, Chris Withers wrote:
> Gary Poster wrote:
>>> Are these any docs on the new features on that branch? If so, where should
>>> I look?
>> The user-visible part of the changes is in the z3c.recipe.scripts recipe
>> contained within the zc.buildout checkout, like zc.rec
Martin v. Löwis wrote:
> > What does "The control ErrorIcon was not found on dialog ErrorDlg" mean?
>
> It probably means it couldn't post the error message for the first
> error, because the icon to indicate "error" isn't included in the MSI
> file (which is a separate bug).
Yes, I started get
Martin v. Löwis wrote:
>
> > The only reference to ErrorIcon was commented out by Martin a while
> > ago. It was the icon attached to the Error Dialog you.
>
> I'm not quite sure why I commented this out. See whether adding it back
> fixes the problem.
Yes, it gets rid of the secondary error,
>>> What's a postinstall script supposed to return or exit
>>> with to indicate success or failure, anyway?
>> It should return 0 as the exit code.
>
> Thanks. What if there's actually an error? Just throw an exception?
Installer will look for a non-zero exit. It will display it as "a action
ha
> Well, in http://svn.python.org/projects/sandbox/branches/MvL/msi/msi.py:
>
># Bitmaps
> add_data(db, "Binary",
> [("PythonWin", msilib.Binary(srcdir+r"\PCbuild\installer.bmp")),
> ("Up",msilib.Binary("Up.bin")),
> ("New",msilib.Binary("New.bin")),
Martin, here's another question. The ability to add pre-install scripts
seems to be implemented:
if self.pre_install_script:
scriptfn = os.path.join(self.bdist_dir, "preinstall.bat")
f = open(scriptfn, "w")
# The batch file will be executed with [PYTHON
> But this doesn't look quite complete. I don't see where the Python
> interpreter is actually invoked here. (Cute trick swapping the args,
> by the way).
>
> Which is presumably why, in finalize_options, we find:
>
> if self.pre_install_script:
> raise DistutilsOptionError,
Martin v. Löwis wrote:
> > But this doesn't look quite complete. I don't see where the Python
> > interpreter is actually invoked here. (Cute trick swapping the args,
> > by the way).
> >
> > Which is presumably why, in finalize_options, we find:
> >
> > if self.pre_install_script:
>
So, in add_ui(), I tried changing
error.control("ErrorIcon", "Icon", 15, 9, 24, 24, 5242881, None,
"py.ico", None, None)
to
error.control("ErrorIcon", "Icon", 15, 9, 24, 24, 5242881, None, None,
None, None)
But I still get this (when I've enabled the pre-install script featur
Martin v. Löwis wrote:
> > But this doesn't look quite complete. I don't see where the Python
> > interpreter is actually invoked here. (Cute trick swapping the args,
> > by the way).
> >
> > Which is presumably why, in finalize_options, we find:
> >
> > if self.pre_install_script:
>
> Looks like we need JScript (what can that do, though?) or VBScript.
Not sure whether users could accept writing JScript or VBScript for
bdist_msi, so (atleast for bdist_msi), I would like to either support
Python pre-install scripts, or not support pre-install scripts at all.
The question is wh
19 matches
Mail list logo
