Re: [Python-Dev] [Distutils] Adventures with x64, VS7 and VS8 on Windows
> The practical problem is: how should 'The PSF' get a Microsoft-signed > certificate? If you want to experiment with a signed installer, try http://www.dcl.hpi.uni-potsdam.de/home/loewis/python-2.5.1.msi In order for Windows to verify the signature, you can install http://www.dcl.hpi.uni-potsdam.de/home/loewis/osm.cer first (and remove it from the list of trusted root certificates when you are done, if you are worried about that). While XP displays the certificate just fine (in Properties/Digital Signatures), my installation of Vista fails to recognize that the file has a signature. Not sure what's wrong here (FWIW, signtool would fail to sign the file as well if run on Vista, but signed it just fine when run on XP). 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] Minor ConfigParser Change
Fred, My only motivation was style. As per your comment: "In general, we try to avoid making style changes to the code since that can increase the maintenance burden (patches can be harder to produce that can be cleanly applied to multiple versions)." I will keep this in mind when supplying future patches. Joseph Armbruster On 5/31/07, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote: On Saturday 26 May 2007, Joseph Armbruster wrote: > I noticed that one of the parts of ConfigParser was not using "for line > in fp" style of readline-ing :-) So, this will reduce the SLOC by 3 > lines and improve readability. However, I did a quick grep and this > type of practice appears in several other places. Before the current iteration support was part of Python, there was no way to iterate over a the way there is now; the code you've dug up is simply from before the current iteration support. (As I'm sure you know.) Is there motivation for these changes other than a stylistic preference for the newer idioms? Keeping the SLOC count down seems pretty minimal, and unimportant. Making the code more understandable is valuable, but it's not clear how much this really achieves that. In general, we try to avoid making style changes to the code since that can increase the maintenance burden (patches can be harder to produce that can be cleanly applied to multiple versions). No other motivat Are there motivations we're missing? -Fred -- Fred L. Drake, Jr. ___ 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] removing use of mimetools, multifile, and rfc822
I just finished going through PEP 4 and adding DeprecationWarnings in 2.6for the various modules that were lacking the warning for some reason or another ... ... except for mimetools, multifile, and rfc822. All three modules are still used by some other module somewhere in the stdlib. The docs say to use the email package to replace these three, but there is no one-to-one mapping. And as I never use any of these three modules, email, or the modules still using the three in question I don't know how to go about ripping them out. In other words this email is to hopefully inspire someone to remove the uses of rfc822, mimetools, and multifile from the stdlib so the DeprecationWarnings can finally go in. -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
Re: [Python-Dev] removing use of mimetools, multifile, and rfc822
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 31, 2007, at 4:09 PM, Brett Cannon wrote: > I just finished going through PEP 4 and adding DeprecationWarnings in > 2.6for the various modules that were lacking the warning for some > reason or > another ... > > ... except for mimetools, multifile, and rfc822. All three modules > are > still used by some other module somewhere in the stdlib. The docs > say to > use the email package to replace these three, but there is no one- > to-one > mapping. And as I never use any of these three modules, email, or the > modules still using the three in question I don't know how to go about > ripping them out. > > In other words this email is to hopefully inspire someone to remove > the uses > of rfc822, mimetools, and multifile from the stdlib so the > DeprecationWarnings can finally go in. +1 for deprecating these. I don't have time to slog through the stdlib and do the work, but I would be happy to help answer questions about alternatives. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRl9BLHEjvBPtnXfVAQKwZgP/aib1PVuLab/YLhCZ+XC82i9ow/tJrelk cLQhcM8Qc/iKcUmFKtKzkhdpOF43dZp6apGrq0ej9pMOdydsFk1wU8egRf+NRJac 00z4ZrMkmM4ZbQ/bNLWHTkqWmadkmTnOErNMl8HzCmbUdBOVNmj6/nzJNT14BRAy K3IRsA6RXzg= =QwId -END PGP SIGNATURE- ___ 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] removing use of mimetools, multifile, and rfc822
On 5/31/07, Barry Warsaw <[EMAIL PROTECTED]> wrote: > > In other words this email is to hopefully inspire someone to remove > > the uses > > of rfc822, mimetools, and multifile from the stdlib so the > > DeprecationWarnings can finally go in. > > +1 for deprecating these. I don't have time to slog through the > stdlib and do the work, but I would be happy to help answer questions > about alternatives. I will give it a shot and will try to come up with a patch. Thanks, Raghu ___ 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] failures in test_sqlite when entire test suite run
I have been getting failures from test_sqlite off the trunk when I run the
entire test suite (as ``./python.exe Lib/test/regrtest.py``) with this error
on OS X 10.4.9 and sqlite3 3.3.16:
Traceback (most recent call last):
File
"/Users/drifty/Dev/python/2.x/pristine/Lib/sqlite3/test/regression.py", line
29, in setUp
self.con = sqlite.connect(":memory:")
ProgrammingError: library routine called out of sequence
When run in isolation it is fine. Anyone have a guess as to what is going
on?
-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
