RE: [Python-Dev] MinGW And The other Py2.4 issue
"Martin v. Löwis" wrote: > Paul Moore wrote: >> Thanks for your comments. Your support for the viability of building >> extensions using mingw is important to me, so if you still have any >> concerns, let me know and I will do my best to address them. > > I understand that one still needs to build libpython24.a in order to > use this process. As I have said, I'd happily ship that file with the > 2.4.1 MSI, unless the release manager tells me that this would an > unacceptable new feature, and as long as somebody provides a fully > automatic build process integrated into msi.py; for that build > process, > it is ok to assume that a cygwin installation is in c:\cygwin. I think we should aim to support MSYS as well as Cygwin, but perhaps not for the first version where this goes in. OTOH, is it really necessary to have either MSYS or Cygwin? MinGW32 works standalone - distutils should be able to just invoke it. Tim Delaney ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
RE: [Python-Dev] MinGW And The other Py2.4 issue
"Martin v. Löwis" wrote: > Not at all. I'm talking about the release process, and prerequisites > required in that process. This is worth mentioning because the list > of prerequisites you need to perform a Python release is already quite > long: Ah - sorry - misinterpreted. What is the size of the generated libpython24.a? Unfortunately, I don't happen to have binutils installed in my work cygwin (pulling it down now, but it's very slow ...) so I can't check myself (I've built the 2.3 one at home before ...). Tim Delaney ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Re: Re: 2.4 news reaches interesting places
> > we should be able to "sell" Python better than we do now, even without > > the need to resort to such poor measures. I'm sure the Python > > community does have good & creative people that can write a good > > "selling" FAQ for Python, emphasizing the main points of the language. > > No one disagrees that Python needs better marketing material. At the > last PyCon a group of people sat down in a pydotorg BoF and agreed > that yes, we do need a management-friendly marketing site, and that we > could put it on a separate hostname (something.python.org) so that the > current www.python.org wouldn't have to be changed. > > However, no one has actually sat down and written such a site, or even > outlined it. Let me encourage you to go ahead and do that. You could > draft the outline on a Wiki page, and then later figure out an > attractive design and organization for a new site. suggested hostname: why.python.org ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] httplib timeout patch
Brett C. wrote: Here is a patch for httplib. I added a timeout value for httplib.HTTPConnection, please check. Thanks for the patch, but this is the wrong place for it. Please create a new patch item on SourceForge at http://sourceforge.net/patch/?group_id=5470 . In addition, also avoid using plain diffs - use context or unified diffs instead. Regards, Martin ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] httplib timeout patch
ZhangYueåå wrote: Hi, Here is a patch for httplib. I added a timeout value for httplib.HTTPConnection, please check. Thanks for the patch, but this is the wrong place for it. Please create a new patch item on SourceForge at http://sourceforge.net/patch/?group_id=5470 . -Brett ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] httplib timeout patch
Hi, Here is a patch for httplib. I added a timeout value for httplib.HTTPConnection, please check. (diff - CVS 1.94) Zhang Yue 2004-12-14 Index: httplib.py === RCS file: /cvsroot/python/python/dist/src/Lib/httplib.py,v retrieving revision 1.94 diff -r1.94 httplib.py 575c575 < def __init__(self, host, port=None, strict=None): --- > def __init__(self, host, port=None, strict=None, timeout=None): 580a581 > self.timeout = timeout 613a615,616 > if self.timeout: > self.sock.settimeout(self.timeout) ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] MinGW And The other Py2.4 issue
Paul Moore wrote: Thanks for your comments. Your support for the viability of building extensions using mingw is important to me, so if you still have any concerns, let me know and I will do my best to address them. I understand that one still needs to build libpython24.a in order to use this process. As I have said, I'd happily ship that file with the 2.4.1 MSI, unless the release manager tells me that this would an unacceptable new feature, and as long as somebody provides a fully automatic build process integrated into msi.py; for that build process, it is ok to assume that a cygwin installation is in c:\cygwin. So if this would be useful (which I don't know for sure), I still need a volunteer to contribute the appropriate magic. Regards, Martin ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] MinGW And The other Py2.4 issue
Delaney, Timothy C (Timothy) wrote: it is ok to assume that a cygwin installation is in c:\cygwin. I think we should aim to support MSYS as well as Cygwin, but perhaps not for the first version where this goes in. Not at all. I'm talking about the release process, and prerequisites required in that process. This is worth mentioning because the list of prerequisites you need to perform a Python release is already quite long: - CVS - putty (for CVS) - VC7.1 - current, built versions of all libraries (zlib, bzip2, tcl/tk, bsddb, ...) - Perl (needed to build OpenSSL) - HTML help workshop - (the platform SDK)(to build Itanium binaries, if desired) Now, I would be willing to add Cygwin on top of that - whether the build process also works with MSYS does not matter to me; I would not like a build process that *required* MSYS as a matter of preference. OTOH, is it really necessary to have either MSYS or Cygwin? MinGW32 works standalone - distutils should be able to just invoke it. I'm not talking about distutils, here. Regards, Martin ___ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
