Martin v. Löwis wrote:
>>> No, I still haven't found a solution. I do want to use the merge
>>> module; anything else probably isn't going to work.
>> Da...ng
>> Didn't you prepare a new MSI installer for 3.0a2 that includes the VS
>> Redist MSM for X86? I vaguely remember that you've replaced my i
>> No, I still haven't found a solution. I do want to use the merge
>> module; anything else probably isn't going to work.
>
> Da...ng
> Didn't you prepare a new MSI installer for 3.0a2 that includes the VS
> Redist MSM for X86? I vaguely remember that you've replaced my installer
> with a new one
Barry Warsaw wrote:
> That would be find with me. Where are those Windows binaries available
> for download from?
The Windows builds are hidden in the development section. It took me 10
minutes to find them because I was searching in the download section and
for nightly builds. The *daily* builds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2008, at 7:11 PM, Christian Heimes wrote:
> Barry Warsaw wrote:
>> From the follow ups, it sounds like others can pitch in here. A
>> question though: is it reasonable to hold up the monthly release
>> because
>> a binary build we're goi
Barry Warsaw wrote:
> From the follow ups, it sounds like others can pitch in here. A
> question though: is it reasonable to hold up the monthly release because
> a binary build we're going to make available can't be done at the same
> time?
>
> My preference (at least for the alphas) is "no". I
Martin v. Löwis wrote:
> No, I still haven't found a solution. I do want to use the merge
> module; anything else probably isn't going to work.
Da...ng
Didn't you prepare a new MSI installer for 3.0a2 that includes the VS
Redist MSM for X86? I vaguely remember that you've replaced my installer
wit
Barry Warsaw <[EMAIL PROTECTED]> writes:
> On Feb 24, 2008, at 1:57 PM, Martin v. Löwis wrote:
>
>>> It very well might. See Christian Heimes's follow up re: Windows
>>> builds. OTOH, I'm okay if at least for the alphas, the binary
>>> builds lag behind the source releases, though I'd like
> Have you solved the problem with the VS CRT redist
> (http://bugs.python.org/issue1569)? Maybe Mark is able to assist you.
No, I still haven't found a solution. I do want to use the merge
module; anything else probably isn't going to work.
Regards,
Martin
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 24, 2008, at 1:57 PM, Martin v. Löwis wrote:
>> It very well might. See Christian Heimes's follow up re: Windows
>> builds. OTOH, I'm okay if at least for the alphas, the binary
>> builds lag behind the source releases, though I'd like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 24, 2008, at 9:19 AM, Christian Heimes wrote:
> Barry Warsaw wrote:
>> I'd also like for us to consider doing regular monthly releases.
>> Several other FLOSS projects I'm involved with are doing this to very
>> good success. The nice thing is
Mark Hammond wrote:
> Me too - I still regularly build the svn version of Python, and although I
> don't regularly turn them into .MSI files, I'm confident I could learn how to
> do that ;) I understand that over time the binary process will need some
> tweaking, but in the general case, I expe
> It very well might. See Christian Heimes's follow up re: Windows
> builds. OTOH, I'm okay if at least for the alphas, the binary builds
> lag behind the source releases, though I'd like to get the process as
> streamlined as possible.
I can continue to provide Windows binaries if desired
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 22, 2008, at 6:54 PM, Brett Cannon wrote:
>> Hi everyone,
>>
>> I've volunteered to be the release manager for Python 2.6 and 3.0.
>> It's been several years since I've RM'd a Python release, and I'm
>> happy to do it again (he says while the m
Barry Warsaw wrote:
> I'd also like for us to consider doing regular monthly releases.
> Several other FLOSS projects I'm involved with are doing this to very
> good success. The nice thing is that everyone knows well in advance
> when the next release is going to happen, and so all developers and
+1 to everything -- n
On Fri, Feb 22, 2008 at 3:45 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> I've volunteered to be the release manager for Python 2.6 and 3.0.
> It's been several years since I've RM'd a Python release, a
On Fri, Feb 22, 2008 at 3:45 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> I've volunteered to be the release manager for Python 2.6 and 3.0.
> It's been several years since I've RM'd a Python release, and I'm
> happy to do i
16 matches
Mail list logo
