Does anyone would like to include Curses support in Windows from version
2.6?
It works ok already using the patch from issue #2889 and PDCurses library,
but needs expertise of core developers to integrate the patch into the build
system, add library to externals to ship next windows Python with emb
> I would really like to see this as release blocker, because the problem
> raised once in a while in the past and the windows people who are
> interested in getting console interface tools usually lack the knowledge
> of unix platform to do the task.
It certainly can't be a release blocker: there
On Sat, May 24, 2008 at 11:48 AM, "Martin v. Löwis" <[EMAIL PROTECTED]>
wrote:
> > I would really like to see this as release blocker, because the problem
> > raised once in a while in the past and the windows people who are
> > interested in getting console interface tools usually lack the knowle
2008/5/24 techtonik <[EMAIL PROTECTED]>:
> Does anyone would like to include Curses support in Windows from version
> 2.6?
I'd like to see this, although it's hardly crucial for me - however,
"from version 2.6" may be unrealistic at this point.
> It works ok already using the patch from issue #28
2008/5/24 techtonik <[EMAIL PROTECTED]>:
>> For this to have any chance, it *must* work with Visual Studio.
>> Requiring gcc is unacceptable.
>
> As for PDCurses library itself there is a Makefile in PDCurses distribution
> for Microsoft Visual C++ 2.0+ named vcwin32.mak I can't afford buying
> Vi
>
> As for PDCurses library itself there is a Makefile in PDCurses distribution
> for Microsoft Visual C++ 2.0+ named vcwin32.mak I can't afford buying
> Visual Studio to test if it works with newer versions, but logically Visual
> Studio should be able to convert Makefile to a newer format.
You
> As for PDCurses library itself there is a Makefile in PDCurses
> distribution for Microsoft Visual C++ 2.0+ named vcwin32.mak I can't
> afford buying Visual Studio to test if it works with newer versions, but
> logically Visual Studio should be able to convert Makefile to a newer
> format.
Visu
> You can start with Visual C++ Express, which is compeltely free ;)
> I don't know if Visual Studio updates the Makefiles.
I would like the makefiles to be ignored entirely. Trent has established
a policy that we compile everything in a single project file, and while
that means some extra work in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can't find any PEP about detailed 2.6 -> 3000 migration guidelines,
specially in the module (C code) extension area. Yes, I know about the
2to3 tool, but I'm interested in updating my 2.x code in order to keep
(automatic via "2to3") difference betwe
On Sat, May 24, 2008 at 9:25 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I can't find any PEP about detailed 2.6 -> 3000 migration guidelines,
> specially in the module (C code) extension area. Yes, I know about the
> 2to3 tool, but I'm interested
10 matches
Mail list logo
