[Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
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 embedded curses support. 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. P.S. It is all about cross-platform roguelikes and text-mode players in Python [1] http://bugs.python.org/issue2889 -- --anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
> 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 is no accepted PEP demanding it, it does not cause any crashes, and it is no regression over earlier releases. For this to have any chance, it *must* work with Visual Studio. Requiring gcc is unacceptable. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
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 knowledge > > of unix platform to do the task. > > It certainly can't be a release blocker: there is no accepted PEP > demanding it, it does not cause any crashes, and it is no regression > over earlier releases. > > 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 Visual Studio to test if it works with newer versions, but logically Visual Studio should be able to convert Makefile to a newer format. As for extension I've provided .bat file that uses GCC for compilation and I think I have some ancient Visual C++ compiler to make the similar .bat file for cl.exe. But I doubt I'll be able to provide a patch for Python build system to compile the module into windows distribution, because I do not have much experience with Python build system and with C linking/makefiles in general. I know that PDCurses must be added to externals/, but that's all. So even if can test and script Python part I am afraid I need help from someone with experience of Python+Make+Visual Studio. -- --anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
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 #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 embedded > curses support. One other option would be to pull out the core curses module as an external project (maybe called "pdcurses"), link it with pdcurses and provide Windows binaries - then developers who cared could do try: import curses except ImportError: import pdcurses as curses > 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. No way it's a release blocker - we've lasted this long without it so it's in no way essential for 2.6. > P.S. It is all about cross-platform roguelikes and text-mode players in > Python Cross-platform any sort of console interface more complex than stdin/stdout. But such interfaces are increasingly rare these days... Paul. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
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 > Visual Studio to test if it works with newer versions, but logically Visual > Studio should be able to convert Makefile to a newer format. Visual C++ 9.0 Express Edition builds Python quite happily these days. So you can certainly do the integration without buying anything. If you get stuck on technical details, there are people here who would happily give you advice. Windows developers are always welcome! > As for extension I've provided .bat file that uses GCC for compilation and I > think I have some ancient Visual C++ compiler to make the similar .bat file > for cl.exe. But I doubt I'll be able to provide a patch for Python build > system to compile the module into windows distribution, because I do not > have much experience with Python build system and with C linking/makefiles > in general. I know that PDCurses must be added to externals/, but that's > all. If you don't have the knowledge needed, and can't spare the time to learn (which is entirely acceptable) then you are indeed relying on another Windows developer to pick this up. You may be out of luck there - nobody has been interested enough to do this before now (it's not as if PDCurses is new) so there's not much reason to expect things to have changed. Paul. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
> > 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 can start with Visual C++ Express, which is compeltely free ;) I don't know if Visual Studio updates the Makefiles. Matthieu -- French PhD student Website : http://matthieu-brucher.developpez.com/ Blogs : http://matt.eifelle.com and http://blog.developpez.com/?blog=92 LinkedIn : http://www.linkedin.com/in/matthieubrucher ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
> 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. Visual Studio 2008 Express is free of charge; so you should be able to work on this with that release. > So even if can test and script Python part I am afraid I need help from > someone with experience of Python+Make+Visual Studio. Then there is little chance that the patch gets accepted. I will have zero time for this until the beta release, unless the patch just needs to be applied, compiles without changes, and passes it the test suite. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issue2889: Add Curses for Windows as native module for 2.6
> 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 initially, it also has advantages (such as not having to worry about conflicting command line options between the library's build procedure, and Python's). Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Any PEP about 2.6 -> 3000 code transition?
-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 between 2.x and 3.x codebase so small as possible. Also, 2to3 doesn't manage migration for C modules. Since I need to port bsddb3 to py3k, what I need to know?. Is any *updated* document out there?. PS: My plan is keep working in the python side under 2.x, and manage Python 3.0 via "2to3", for a long time. In the C side, I plan keeping the same codebase, with conditional compilation. Ideas?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[EMAIL PROTECTED] _/_/_/_/ _/_/_/_/_/ ~ _/_/ _/_/_/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBSDjqJplgi5GaxT1NAQLP3QP/Y2bWmNzHKsIq23dRz9sxd237TSfzbs5X UzEQ6Ze9Kv1lRXYRfiGjk37aOeiO4xqoKPfASc/WjMN/TmRkUNZxMQEQWwFYhmCA aAVqGxNMEX3KCXvRP9MkkZYLPa9RZg8boPTMYCn+uLDW1Ff2Pwj96hFKbWKG0dkJ RamNp8BFhkM= =ngK+ -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Any PEP about 2.6 -> 3000 code transition?
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 in updating my 2.x code in order to keep > (automatic via "2to3") difference between 2.x and 3.x codebase so small > as possible. Also, 2to3 doesn't manage migration for C modules. > > Since I need to port bsddb3 to py3k, what I need to know?. Is any > *updated* document out there?. > No definitive porting guide has been written, although it has been discussed as being needed before. One should probably be written ASAP if we are going to get any decent testing done by people with the beta (and I am definitely NOT volunteering to write the doc). -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
