[EMAIL PROTECTED] wrote:
> On Feb 13, 2:24 am, Steve Holden <[EMAIL PROTECTED]> wrote:
[...]
This wouldn't be a simple project, but since there's a Windows buildbot
for Python there's no reason why the same couldn't be done for
extensions. I'll raise this with the PSF and see what th
On Feb 13, 2:24 am, Steve Holden <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > On Feb 11, 4:24 am, Steve Holden <[EMAIL PROTECTED]> wrote:
> >> [EMAIL PROTECTED] wrote:
> >>> On Feb 11, 1:35?am, Steve Holden <[EMAIL PROTECTED]> wrote:
> [...]
>
> >>> By the way, on the sci.math newsgrou
[EMAIL PROTECTED] wrote:
> On Feb 11, 4:24 am, Steve Holden <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] wrote:
>>> On Feb 11, 1:35?am, Steve Holden <[EMAIL PROTECTED]> wrote:
[...]
>
>>> By the way, on the sci.math newsgroup I promote
>>> Python every chance I get. One fellow thanked me
>>> pr
On Feb 11, 5:33?am, Steven D'Aprano
<[EMAIL PROTECTED]> wrote:
> On Sun, 11 Feb 2007 01:08:21 -0800, [EMAIL PROTECTED] wrote:
> >> An update is in the works for those
> >> using more recent releases,
>
> > That's good news, although the responsible thing
> > to do was not relaease version 2.5 until
On Feb 11, 4:24 am, Steve Holden <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > On Feb 11, 1:35?am, Steve Holden <[EMAIL PROTECTED]> wrote:
> [...]
> After all, they have already given freely and generously, and if they
> choose
> not to give more on top of that, it's rea
On Sun, 11 Feb 2007 01:08:21 -0800, [EMAIL PROTECTED] wrote:
>> An update is in the works for those
>> using more recent releases,
>
> That's good news, although the responsible thing
> to do was not relaease version 2.5 until such issues
> are resolved.
I realize you're a Windows user, and a Wi
[EMAIL PROTECTED] wrote:
> On Feb 11, 1:35�am, Steve Holden <[EMAIL PROTECTED]> wrote:
[...]
After all, they have already given freely and generously, and if they
choose
not to give more on top of that, it's really up to them.
>>> Right. Get people to commit and then abandon them. N
On Feb 11, 1:35�am, Steve Holden <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > On Feb 10, 4:07?pm, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
> >> On Feb 10, 6:31 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> >>> On Feb 9, 11:39?am, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
> Hop
"Ben Sizer" <[EMAIL PROTECTED]> wrote:
> On Feb 10, 8:42 am, Steve Holden <[EMAIL PROTECTED]> wrote:
> > Hendrik van Rooyen wrote:
> > > <[EMAIL PROTECTED]> wrote:
> > > "Ben Sizer" <[EMAIL PROTECTED]> wrote:
> >
> > >> Ben> Python extensions written in C require recompilation for each
new
>
[EMAIL PROTECTED] wrote:
> On Feb 10, 4:07?pm, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
>> On Feb 10, 6:31 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>>
>>> On Feb 9, 11:39?am, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
Hopefully in the future, some of those convoluted steps will be fixed,
>
Ben Sizer wrote:
> On Feb 10, 8:42 am, Steve Holden <[EMAIL PROTECTED]> wrote:
>> Hendrik van Rooyen wrote:
>>> <[EMAIL PROTECTED]> wrote:
>>> "Ben Sizer" <[EMAIL PROTECTED]> wrote:
Ben> Python extensions written in C require recompilation for each new
Ben> version of Python, due
"Steve Holden" <[EMAIL PROTECTED]>
> Hendrik van Rooyen wrote:
> > <[EMAIL PROTECTED]> wrote:
> > "Ben Sizer" <[EMAIL PROTECTED]> wrote:
> >
> >
> >> Ben> Python extensions written in C require recompilation for each new
> >> Ben> version of Python, due to Python limitations.
> >>
> >> C
On Feb 10, 11:03�pm, [EMAIL PROTECTED] wrote:
> � � >> However, the difference between the open-source people and Microsoft
> � � >> is the the open-source people aren't being paid by you for the use of
> � � >> their product, so they're not obligated in any way to help you.
>
> � � mensanator> Thi
>> However, the difference between the open-source people and Microsoft
>> is the the open-source people aren't being paid by you for the use of
>> their product, so they're not obligated in any way to help you.
mensanator> This argument has become tiresome. The Python community
On Feb 10, 4:07?pm, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
> On Feb 10, 6:31 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > On Feb 9, 11:39?am, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
>
> > > Hopefully in the future, some of those convoluted steps will be fixed,
> > > but that requires som
On Feb 10, 8:42 am, Steve Holden <[EMAIL PROTECTED]> wrote:
> Hendrik van Rooyen wrote:
> > <[EMAIL PROTECTED]> wrote:
> > "Ben Sizer" <[EMAIL PROTECTED]> wrote:
>
> >> Ben> Python extensions written in C require recompilation for each new
> >> Ben> version of Python, due to Python limitati
On Feb 10, 6:31 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> On Feb 9, 11:39?am, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
>
> > Hopefully in the future, some of those convoluted steps will be fixed,
> > but that requires someone putting in the effort to do so. As is often
> > the case with Py
Siggi> ... I conclude now that I will be better off to drop Windows and
Siggi> install Linux on my next PC, to be able to reap the full benefits
Siggi> of Python.
Darn tootin'... (*)
Skip
(*) http://en.wikipedia.org/wiki/You're_Darn_Tootin'
--
http://mail.python.org/mailman/listin
>> Python used to work that way. You'd then silently get errors if the
>> API changed between version A and version B and you neglected to
>> recompile the extensions you compiled against version A.
bearophile> Can't the compiled module have one or more test functions
bearoph
Hendrik van Rooyen wrote:
> <[EMAIL PROTECTED]> wrote:
> "Ben Sizer" <[EMAIL PROTECTED]> wrote:
>
>
>> Ben> Python extensions written in C require recompilation for each new
>> Ben> version of Python, due to Python limitations.
>>
>> Can you propose a means to eliminate this limitation?
>
"Ben Sizer" wrote:
[snip]
> Hopefully in the future, some of those convoluted steps will be fixed,
> but that requires someone putting in the effort to do so. As is often
> the case with Python, and indeed many open source projects, the people
> who are knowledgeable enough to do such things usuall
On Feb 9, 11:39�am, "Ben Sizer" <[EMAIL PROTECTED]> wrote:
> On Feb 9, 1:48 pm, "siggi" <[EMAIL PROTECTED]> wrote:
>
> > @Ben Sizer
>
> Lucky I spotted this...
>
> > As a Python (and programming ) newbie �allow me a �- certainly naive -
> > question:
>
> > What is this time consuming part of recomp
<[EMAIL PROTECTED]> wrote:
"Ben Sizer" <[EMAIL PROTECTED]> wrote:
> Ben> Python extensions written in C require recompilation for each new
> Ben> version of Python, due to Python limitations.
>
> Can you propose a means to eliminate this limitation?
>
Yes. - Instead of calling someth
On Feb 9, 9:01 pm, [EMAIL PROTECTED] wrote:
> Ben> If someone could explain the limitation in detail, I expect ways
> Ben> could be found around it. After all, I don't know of any other
> Ben> systems that require you to recompile all the extensions when you
> Ben> upgrade the appli
Skip:
> Python used to work that way. You'd then silently get errors if the API
> changed between version A and version B and you neglected to recompile the
> extensions you compiled against version A.
Can't the compiled module have one or more test functions that can be
used during linking to se
Ben> If someone could explain the limitation in detail, I expect ways
Ben> could be found around it. After all, I don't know of any other
Ben> systems that require you to recompile all the extensions when you
Ben> upgrade the application.
Python used to work that way. You'd then
On Feb 9, 5:53 pm, [EMAIL PROTECTED] wrote:
> Ben> Python extensions written in C require recompilation for each new
> Ben> version of Python, due to Python limitations.
>
> Can you propose a means to eliminate this limitation?
By putting an intermediate layer between the extensions and th
Ben> Python extensions written in C require recompilation for each new
Ben> version of Python, due to Python limitations.
>> Can you propose a means to eliminate this limitation?
Mike> Sure, write your wrapper-style extensions in ctypes :).
I was think more along the lines of ho
[EMAIL PROTECTED] wrote:
> Ben> Python extensions written in C require recompilation for each new
> Ben> version of Python, due to Python limitations.
>
> Can you propose a means to eliminate this limitation?
>
Sure, write your wrapper-style extensions in ctypes :) . For example,
pygam
Ben Sizer wrote:
> The problem is something like this:
> - Python extensions written in C require recompilation for each new
> version of Python, due to Python limitations.
> - Recompiling such an extension requires you to have a C compiler set
> up on your local machine.
> - Windows doesn't co
Ben> Python extensions written in C require recompilation for each new
Ben> version of Python, due to Python limitations.
Can you propose a means to eliminate this limitation?
Skip
--
http://mail.python.org/mailman/listinfo/python-list
On Feb 9, 1:48 pm, "siggi" <[EMAIL PROTECTED]> wrote:
> @Ben Sizer
Lucky I spotted this...
> As a Python (and programming ) newbie allow me a - certainly naive -
> question:
>
> What is this time consuming part of recompiling an extension, such as
> Pygame, from source code to Windows? Is it a
Thanks, I'll try that!
Siggi
"Laurent Pointal" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
> siggi a écrit :
>> Hi all,
>>
>> when I rtry to install pygame (pygame-1.7.1release.win32-py2.4.exe, the
>> most
>> ciurrent version I found) it requires Python 2.4! Will I really ha
siggi a écrit :
> Hi all,
>
> when I rtry to install pygame (pygame-1.7.1release.win32-py2.4.exe, the most
> ciurrent version I found) it requires Python 2.4! Will I really have to
> uninstall my Python 2.5 and install the old Python 2.4 in order to use
> pygame?
Note: You can have both versions
siggi wrote:
> when I rtry to install pygame (pygame-1.7.1release.win32-py2.4.exe, the most
> ciurrent version I found) it requires Python 2.4! Will I really have to
> uninstall my Python 2.5 and install the old Python 2.4 in order to use
> pygame?
For now, yes. This is a long-standing problem w
35 matches
Mail list logo
