fyi - i've updated the python sha1/md5 openssl patch. it now replaces
the entire sha and md5 modules with a generic hashes module that gives
access to all of the hash algorithms supported by OpenSSL (including
appropriate legacy interface wrappers and falling back to the old code
when compiled wit
On Fri, Feb 18, 2005 at 10:06:24AM +0100, "Martin v. L?wis" wrote:
> Donovan Baarda wrote:
> >This patch keeps the current md5c.c, md5module.c files and adds the
> >following; _hashopenssl.c, hashes.py, md5.py, sha.py.
> [...]
> >If all we wanted to do was fix the md5 module
>
> If we want to fix
On Fri, Mar 11, 2005 at 06:47:11PM -0500, Bob Ippolito wrote:
>
> On Mar 11, 2005, at 2:26 PM, Skip Montanaro wrote:
>
> >
> >Bob> try:
> >Bob> set
> >Bob> except NameError:
> >Bob> from sets import Set as set
> >
> >Bob> You don't need the rest.
> >
> >Sure, but the
> [Gregory P. Smith]
> > or make it even uglier to hide from pychecker by writing that as:
> >
> > exec("""
> > try:
> > set
> > except NameError:
> > from sets import Set as set
> > """)
>
> > Under "Limitations and Exclusions" it specifically disowns
> > responsibility for worrying about whether Py_Initialize() and
> > PyEval_InitThreads() have been called:
> >
> [snip quote]
>
> This suggests that I should call PyEval_InitThreads() in
> initreadline(), which seems daft.
fwiw, Mod
On Tue, Jun 07, 2005 at 08:49:11PM +0200, Irmen de Jong wrote:
> furthermore the 'make install' of current cvs fails halfway trough
> with the following errors:
>
>.
>.
> Compiling /opt/python25/lib/python2.5/bsddb/test/test_associate.py ...
> Sorry: TabError: ('inconsistent use of
I have finished up the hashlib work I started on in feb/march for
patch 1121611 and 935454 after some discussion on this list. The full
patch including tests and module documentation has been posted in the
sf patch 1121611 as hashlib-008.
I believe it is done and ready and would like to commit it
On Wed, Mar 08, 2006 at 03:03:48AM +0100, Thomas Wouters wrote:
> On 3/7/06, "Martin v. L??wis" <[EMAIL PROTECTED]> wrote:
> >
> > Thomas Wouters wrote:
> > > Who 'owns' Modules/_bsddb.c, if anyone?
> >
> > It's a fork of pybsddb, originally contributed by Gregory Smith (*).
> > For all practical p
On Sat, Mar 11, 2006 at 07:08:14PM +0100, Thomas Heller wrote:
> Martin v. L?wis wrote:
> > Josiah Carlson told me had has given up getting a Windows
> > buildbot running, because every time he installed VS.NET
> > on his machine, the installation would immediately crash.
> >
> > So if anybody wan
On Sun, Mar 12, 2006 at 06:48:13PM -0500, Tim Peters wrote:
> [Trent]
> > :)
> > Did you apply the Berkeley DB patches to your db-4.2.52 sources?
>
> Ah, _which_ patches? As with my buildbot Wiki page, I write down
> everything I do if there's a good chance I may need to do it again.
> So, e.g.,
> The language choice should only be used as an argument if all else is
> equal. Of course, "hackability" of a particular solution may be a
> criterion too, and there the language choice could matter. But the
> above response sounded like a knee-jerk to me, and IMO needs to be
> rebutted.
>
> --
>
On Wed, Mar 29, 2006 at 03:35:48PM +0200, Gerhard H?ring wrote:
> Barry Warsaw wrote:
> > On Wed, 2006-03-29 at 19:47 +1100, Anthony Baxter wrote:
> >
> >>My only concern about this is that it wouldn't be possible for other
> >>authors to provide 3rd party packages as (for instance) db.mysqldb
>
On Wed, Mar 29, 2006 at 11:47:10PM +0200, Thomas Wouters wrote:
> Con:
> > * Competing Python wrappers exist
> > * SQLite itself is updated frequently, let alone the wrappers
> > * Build integration risks unknown, possible delay of 2.5?
> > * Another external library to track and maybe have emergen
> Getting off on a tangent here, but I would actually
> like some decent way of writing SQL queries in Python --
> not for importing, but for database access.
>
> Constructing bits of SQL out of character strings
> sucks *extremely* badly.
Have you looked at SqlObject? (and its associated module
On Sat, Apr 08, 2006 at 02:47:28PM -0700, Brett Cannon wrote:
> OK, I am going to write the PEP I proposed a week or so ago, listing
> all modules and packages within the stdlib that are maintained
> externally so we have a central place to go for contact info or where
> to report bugs on issues.
> Module names like hashlib are not python-like too (too c/lowlevel-like).
what is python-like?
hashlib was chosen because it is a library of hash functions and
hash() is already taken as a builtin function (otherwise i'd leave off
the lib).
-g
___
Pyt
> As I mentioned earlier I'd like to get patch 1446489 (support for
> zip64 extensions in the zipfile module) in python 2.5. The patch
> should be perfectly safe, it comes with unittests and a documentation
> update. I'm also using this version of zipfile in (closed-source)
> projects to ha
On Sat, Jun 17, 2006 at 03:27:36PM +0200, "Martin v. L?wis" wrote:
> Scott Dial wrote:
> >> For fopen(3), you are right. For signal(3), VS2005 is in clear
> >> violation with ISO C
> >
> > I'm nobody but I don't find your argument compelling. I suggest you go
> > read: http://msdn2.microsoft.com/e
os.path.getmtime returns a float on linux (2.5a2/b1 HEAD); in 2.4 it
returned an int. this change makes sense, its what time.time returns.
should there be a note in Misc/NEWS or whatsnew mentioning this minor
change (or did i miss it)? It breaks code that unintentionally
depended on it returning
https://sourceforge.net/tracker/index.php?func=detail&aid=1121611&group_id=5470&atid=305470
This is the hashlib module that speeds up python's md5 and sha1
support by using openssl (when available) as well as adding sha224/256
+ sha384/512 support (plus anything openssl provides).
I believe it is
On Mon, Aug 22, 2005 at 08:46:27AM -0400, Raymond Hettinger wrote:
> > A new hashlib module to replace the md5 and sha modules. It adds
> > support for additional secure hashes such as SHA-256 and SHA-512. The
> > hashlib module uses OpenSSL for fast platform optimized
> > implementations of algo
> This patch should be reverted or fixed so that the Py2.5 build works
> again.
>
> It contains a disasterous search and replace error that prevents it from
> compiling. Hence, it couldn't have passed the test suite before being
> checked in.
>
> Also, all of the project and config files need
> The project files are just text files and can be updated simply and
> directly. But yes, that is no big deal and I'll just do it for him once
> the code gets to a compilable state.
I just checked in an update removing all of the ULLs. Could you check
that it compiles on windows and passes test
On Mon, Sep 19, 2005 at 09:12:05PM +0100, Michael Hudson wrote:
> Martin Blais <[EMAIL PROTECTED]> writes:
> > On 9/18/05, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> >> On 9/17/05, John J Lee <[EMAIL PROTECTED]> wrote:
> >> > I realize that not all algorithms (nor all computational problems) sca
On Fri, Dec 16, 2005 at 02:50:36PM -0800, Brett Cannon wrote:
> On 12/16/05, Tim Peters <[EMAIL PROTECTED]> wrote:
> [SNIP]
> > python-dev'ers: I failed to find anything in the trunk's NEWS file
> > about this (neither about `hashlib`, nor about any of the specific new
> > hash functions). It's n
On Sun, Dec 18, 2005 at 11:09:54AM +0100, "Martin v. L?wis" wrote:
> Thomas (Heller) and I have been discussing whether the zlib
> module should become builtin, atleast on Win32 (i.e. part
> of python25.dll). This would simplify py2exe, which then could
> bootstrap extraction from the compressed fi
> A new core `hashlib` module will be included in Python 2.5, but will
> not be backported to older Python versions. It includes new
> implementations for SHA-224, -256, -384 and -512. The code and tests
> are already written, and can be gotten from Python's SVN trunk.
Another thing I intended t
On Sun, Jan 22, 2006 at 11:01:36PM -0800, Neal Norwitz wrote:
> rather than later. There are a bunch of tests that are not stable.
> It would really help to get people knowledgeable about a particular
> subdomain to provide input into bugs/patches and produce patches too!
>
> The areas that are
601 - 628 of 628 matches
Mail list logo
