Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11380/sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Attaching test cases based on dumbdbm tests.
Added file: http://bugs.python.org/file11384/test_dbm_sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Another slight revision to the module.
Added file: http://bugs.python.org/file11385/sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11383/sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Trivial doc diffs against 3.0b3 doc.
Added file: http://bugs.python.org/file11386/dbm.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Another tweak - add values()
Added file: http://bugs.python.org/file11387/sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Updated test cases
Added file: http://bugs.python.org/file11388/test_dbm_sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11384/test_dbm_sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11385/sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Antoine> It would be more efficient to base keys() on iterkeys() than the
Antoine> reverse, IMO.
True. I was just modifying the dumbdbm implementation.
Antoine> Other than that, why not open a branch or at least upl
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
OK, I made a sandbox project out of it:
svn+ssh://[EMAIL PROTECTED]/sandbox/trunk/dbm_sqlite
Hack away!
--
assignee: -> skip.montanaro
___
Python tracker <[EMAIL PROTE
Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11386/dbm.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11387/sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11388/test_dbm_sqlite.py
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Skip Montanaro <[EMAIL PROTECTED]>:
Consider these two timeit commands:
py3k% python3.0 -m timeit -s 'import dbm.ndbm as db' -s 'f =
db.open("/tmp/trash.db", "c")' 'for i in range(1000): f[str(i)] = str(i)'
100 loops,
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Extra data point. I tried
f["1"] = "a"
and
f[b"1"] = "a"
with dbm.{gnu,ndbm,dumb,sqlite}. All worked with bytes. A except
dbm.dumb worked with strings. (dbm.sqlite is my little pr
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
I'm not sure. I've never done anything with the io module. Simply
eliminating the bytes checks and letting it try to write the string
yields:
File "/Users/skip/local/lib/python3.0/dbm/dumb.py", line 170, in
__
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Just a quick nit, but it seems to me that since 2.6 still actually
distinguishes between longs and ints that the two error messages in
PyLong_FromFloat should mention "long" instead of "integer".
Skip
--
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Amaury> I suppose you meant PyLong_FromDouble()?
Yes, sorry.
Amaury> I think the messages talk about abstract numbers, not a specific
Amaury> python type: "infinity/NaN cannot be converted to an integral
A
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Gerhard> What's all this ORDER BY in both your implementations about?
Gerhard> The dbm "spec" says nothing about keys being ordered AFAIC. Can
Gerhard> we get rid of these?
I'd like to guar
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
>> I'd like to guarantee that zip(db.keys(), db.values() == db.items().
Antoine> It doesn't sound very useful, and it may hurt performance on
Antoine> big tables.
Actually, I think Python guarantees
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Gerhard> FWIW that will also work without the ORDER BY, because you're
Gerhard> getting the rows back in the same ORDER. Something cheaper
Gerhard> would also be "ORDER BY ROWID". I still propose to ju
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
>> As long as SQLite guarantees that the ordering is identical, then
>> sure, dump the ORDER BY clause.
Gerhard> It doesn't guarantee it, but the implementation behaves like
Gerhard> this.
If the
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Antoine> I might add that calling keys() then values() is suboptimal,
Antoine> because it will issue two SQL queries while calling items()
Antoine> will issue just one.
Well, sure, but heaven only knows what an applica
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
>> Well, sure, but heaven only knows what an application programmer will
>> do...
Antoine> If the docs clearly explain that there is no guarantee, we
Antoine> don't need heaven. I would find i
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Josiah> I know that no one hear likes my particular implementation
Josiah> (though it offers more or less the full interface)...
I think implementing as much of the bsddb interface as you can is fine. I
agree people used
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
What would you suggest? The docs already say:
Though list objects support similar operations, they are optimized
for fast fixed-length operations and incur O(n) memory movement costs
for pop(0) and insert(0, v) operations which
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Why not just have atexit_callfuncs call atexit_cleanup at the end of its
execution?
--
nosy: +skip.montanaro
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
The attached patch causes an exception to print
at exit on my Mac:
>>> import sys, atexit
>>> atexit.register(lambda: 1, 0, 0, (x for x in (1,2)), 0, 0)
at 0x5c91e0>
>>> sys.exit()
Error in atexit._run_e
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
New patch. This also makes the various atexit_*
functions static.
Added file: http://bugs.python.org/file11519/atexit.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Skip Montanaro <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11517/atexit.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
I've taken this ticket. Can someone please review and give
it a thumbs up or thumbs down?
--
assignee: -> skip.montanaro
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Checked in as revision 66562.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Looks reasonable, though I'm no ctypes maven. Trivial little nit:
In the comment just before the start of CField_FromDesc it says,
in part:
* Expects the size, index and offset for the current field in *psize and
* *poffset,
New submission from Skip Montanaro <[EMAIL PROTECTED]>:
The "clean" target in the makefile fails to delete the libpython.a file
and the libpython.so.X.Y file (should you have configured using
--enable-shared). The attached trivial patch solves that problem.
The patch is against
New submission from Skip Montanaro <[EMAIL PROTECTED]>:
If you are fortunate enough to have all your third-party libraries in
a single quasi-standard location, say, /usr/local/lib, you will
probably have never encountered this problem, but setting environment
variables like LDFLAGS don
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Brett> Well, all of my modules are in a non-standard location and I have
Brett> no build issues on OS X 10.5. If you look at
Brett> PyBuildExt.detect_modules() you will see that the paths are at
Brett> least ad
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Here's a patch. Works for me on Solaris 10. I'll try to check
it out on OS X 10.5. Would appreciate it if someone on Linux can
kick the tires too.
--
keywords: +easy, patch
Added file: http://bugs.python.org/file11
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Confirmed that nothing seems broken on my OS X 10.5 laptop (doing a
unix-style build, not a framework build).
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Seems to work for framework builds as well.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
I checked in r66823 to add the -R flag extraction like Brett's -L
extraction. I'll leave the issue open while folks discuss Roumen's
proposal. I have no particular desire to delve d
New submission from Skip Montanaro <[EMAIL PROTECTED]>:
While responding to a c.l.py question just now I discovered that
numeric timezone offsets don't appear to be supported by either the
time.strftime function or the _strptime module. I noticed on my
Mac's strftime(3)
New submission from Skip Montanaro <[EMAIL PROTECTED]>:
I worked up a simple example of using the external processing module
(0.52) for a friend at work today. I noticed some cases where it raised
exceptions during exit. Not all the time, but not infrequently either.
This evening I t
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Oh, the range command used in the shell for loop is analogous to Python's
range() builtin function.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Got another one just now, but with just the note about the exception
in the queue feeder thread. The traceback was swallowed.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro <[EMAIL PROTECTED]> added the comment:
Final comment before I see some feedback from the experts.
I have this code in the worker function's loop:
# quick pause to allow other stuff to happen a bit randomly
t = 0.1 * random.random()
time.sleep(t)
If I el
Skip Montanaro added the comment:
This is to be expected. The Error Exception is actually defined in the
underlying _csv extension module. The higher level csv Python module
imports it. The two are the same object:
>>> import csv, _csv
>>> csv.Error
>>> _
Skip Montanaro added the comment:
Looks good to me:
tmp% python3.1 popentest.py
time with os.popen : 0.035565
time with subprocess.Popen : 0.031796
tmp% python3.2 popentest.py
time with os.popen : 0.03501
time with subprocess.Popen : 0.031168
tmp% python3.1
Python 3.1.1+ (release31-maint
Skip Montanaro added the comment:
Amaury> Comment lines in csv data may be common in some areas, but they
Amaury> are not part of any standard, and they are not the only possible
Amaury> extension to csv files (for example: ignore empty lines, or a
Amaury> termina
Skip Montanaro added the comment:
Antoine> Since the csv module returns you an iterator, it's easy enough
Antoine> to wrap it in another iterator.
I prefer to do this sort of stuff as a pre-processing step, so I generally
wrap the file object input and use that iterator as the
Skip Montanaro added the comment:
John> Current OpenBSD is at 4.7 with a new release every six months.
John> diff below:
...
John> - OpenBSD/2.* | OpenBSD/3.[0123456789] | OpenBSD/4.[0123])
John> + OpenBSD/2.* | OpenBSD/3.* | OpenBSD/4.[01234567])
Wouldn'
Skip Montanaro added the comment:
>> Yeah or better yet take out the versioning entirely.
Perhaps. Is 1.x treated differently than 2, 3 or 4?
S
--
___
Python tracker
<http://bugs.python.org/
Skip Montanaro added the comment:
Jesus> can I ask if this (very useful) feature is on time for Python 2.7?
You can ask, but I suspect you'd be disappointed in the answer. Do you have
time to look at the issue? The biggest sticking point in my mind is coming
up with a uniform set o
New submission from Skip Montanaro :
I don't know where this will go given that it's not a response to an
existing bug report. I'm looking to see if the SpamBayes instance on
mail.python.org processes this message.
Someone please respond to let me know if this address is working
New submission from Skip Montanaro :
After training a bunch of mail held for python-bugs-list I'm trying another
post to see how well SpamBayes likes it.
Skip
--
messages: 100482
nosy: skip.montanaro
severity: normal
status: open
title: Te
Skip Montanaro added the comment:
Test successful...
--
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Skip Montanaro added the comment:
I don't know, but it's quite possible. Lots of messages were held for
moderation. It's possible that some were rejected as spam.
--
___
Python tracker
<http://bugs.py
New submission from Skip Montanaro :
I svn up'd and rebuild the release26-maint branch today on my Mac (MacBook
Pro, OSX 10.5.8). test_asynchat and test_smtplib both fail with
unexpected output:
test test_asynchat produced unexpected o
Skip Montanaro added the comment:
Ned> Neither of these problems are new to Python 2.6.5: see Issue7037
Ned> (test_asynchat) and Issue7040 (test_smtplib).
Thanks. I searched for "asynchat" and "smtplib" but
Changes by Skip Montanaro :
--
resolution: -> duplicate
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8141>
___
___
Python-bugs-
Changes by Skip Montanaro :
--
nosy: -skip.montanaro
___
Python tracker
<http://bugs.python.org/issue3783>
___
___
Python-bugs-list mailing list
Unsubscribe:
Skip Montanaro added the comment:
Martin> If it did eat the patch, we would have lost it by now: there is
Martin> nothing in the history that shows that a file was attached at
Martin> some point. More likely, Skip forgot to attach it when
Martin> submitting this repo
Skip Montanaro added the comment:
Type conversion is a whole 'nuther kettle of fish. This particular thread is
long and complex enough that it shouldn't be made more complex.
--
___
Python tracker
<http://bugs.python.
Skip Montanaro added the comment:
It's clear you can't change it for 2.6 or 2.7, almost certainly not 3.1.
Maybe you could change it for 3.2.
--
nosy: +skip.montanaro
___
Python tracker
<http://bugs.python.
Skip Montanaro added the comment:
Whoops. No stringio.py in 3.x. This should be closed as won't fix since it's
not a problem in py3k and can't be changed in 2.x.
--
___
Python tracker
<http://bugs.py
New submission from Skip Montanaro :
At work we are in the process of migrating from Python 2.4 to 2.6. One
bit of Boost.Python code needs to use PyImport_ImportModuleLevel which
references the __import__ docs. That describes the use of the level arg.
I then went around looking for examples
Skip Montanaro added the comment:
The attached diff adds a PackageTest class which exercises
both "from . import blah" and its __import__() equivalent.
The diff is against the release26-maint branch but I
suspect it will apply cleanly to trunk and probably py3k.
--
keywor
Skip Montanaro added the comment:
Unassigning so someone else can pick it up and review to
see if this makes sense.
--
assignee: skip.montanaro ->
___
Python tracker
<http://bugs.python.org/iss
New submission from Skip Montanaro :
The topic of the vileness of Fink or MacPorts came up in python-dev when
discussing building a Mac installer. I remembered that a couple /sw and
/opt/local directories are searched unconditionally, making it a bit
more challenging for someone to create a
Skip Montanaro added the comment:
Let's try this again.
--
keywords: +patch
Added file: http://bugs.python.org/file16930/setup.diff
___
Python tracker
<http://bugs.python.org/i
Skip Montanaro added the comment:
The patches referenced in issue7713 just unconditionally delete certain
directories from the search path(s). This patch (now attached) allows
the user to control that. I presume, for instance, if the MacPorts
folks don't want /usr/X11/... in search paths
Skip Montanaro added the comment:
Ronald> To be honest I'd must rather remove /opt/local and /sw entirely
Ronald> from setup.py and add new configure flags to specify the
Ronald> location of a number of libraries (e.g. 'configure
Ronald> --with-sleepycat-db=/
Skip Montanaro added the comment:
Mark> I think it's fine to do the division and round the result to the
Mark> nearest whole number of microseconds.
Right. Just think of a timedelta as a floating point number of seconds with
very limited precision (1
Skip Montanaro added the comment:
Maybe the wording should be changed, but name mangling serves a useful
purpose. There are two definitions of "private" which seem to be a
bit conflated in this section:
* "private" as in, "this name is not part of the public API -
Skip Montanaro added the comment:
mal> Interesting. It appears as if r57142 caused this change.
How do I get a diff of the change in r57142? In particular, is it something
I did? I was working on deleting BeOS support (and support for other
minority platforms) awhile ago. I don'
Skip Montanaro added the comment:
mal> Interesting. It appears as if r57142 caused this change.
Skip> How do I get a diff of the change in r57142?
Okay, I got that diff. The change was from my BeOS cleaning. While adding
back in that ifdef certain restores the desired behavior, I
Skip Montanaro added the comment:
Chris> I keep needing to know the number of seconds that a timedelta
Chris> represents, so I implemented the following patch.
I can sympathize, but if we accept this patch, for symmetry reasons
shouldn't we also add .todays, .tomicroseconds and
New submission from Skip Montanaro:
The topic of avoiding string copies in certain string methods came up in
the
ChiPy list:
http://mail.python.org/pipermail/chicago/2007-December/002975.html.
The attached patch modifies the split and rsplit implementations to
avoid
making a copy of self
Skip Montanaro added the comment:
I'm not sure why a string subclass shouldn't work, but I've attached a new
version of the patch that calls PyString_CheckExact() to prevent using a
string subclass.
Added file: http://bugs.python.org/file8864/str
Changes by Skip Montanaro:
Removed file: http://bugs.python.org/file8851/string-split.patch
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1538>
__
___
Pyth
Skip Montanaro added the comment:
In the absence of any more feedback, I checked this in as r59420.
--
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro added the comment:
updated docstrings for file and open (r59417).
--
nosy: +skip.montanaro
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro added the comment:
Okay, here's my latest patch (datetime-f.diff). 2.6 only at this point.
Added file: http://bugs.python.org/file8901/datetime-f.diff
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Changes by Skip Montanaro:
Removed file: http://bugs.python.org/file8438/dt-26.diff
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1158>
__
___
Python-bugs-list
Skip Montanaro added the comment:
Actually, I think I will avoid the 3.0 patch altogether and let these
changes propagate from trunk to py3k by whoever works that magic.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Skip Montanaro added the comment:
Updated diff. Just a tweak to datetime.rst.
Added file: http://bugs.python.org/file8903/datetime-f.diff
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1158>
__Index:
Changes by Skip Montanaro:
Removed file: http://bugs.python.org/file8439/dt-30.diff
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1158>
__
___
Python-bugs-list
Changes by Skip Montanaro:
Removed file: http://bugs.python.org/file8901/datetime-f.diff
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1158>
__
___
Python-bugs-
Skip Montanaro added the comment:
Stop me before I update it again! This update touches up
datetime_strptime a bit. It's more uniform and a bit faster.
Added file: http://bugs.python.org/file8907/datetime-f.diff
__
Tracker <[EMAIL PROTECTED
Changes by Skip Montanaro:
Removed file: http://bugs.python.org/file8903/datetime-f.diff
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1158>
__
___
Python-bugs-
Skip Montanaro added the comment:
Guido> ... trying to explain why two numbers both print the same but
Guido> compare unequal ...
This is not a Python-specific issue. The notion of limited precision was
pounded into our heads in the numerical analysis class I took in college,
19
New submission from Skip Montanaro:
(third try at getting this bug report to submit by email.)
While riding to work today I ran the test suite on trunk. The following
tests failed due to lack of network connectivity:
test_socket
test_socket_ssl
test_ssl
test_urllib2
These
New submission from Skip Montanaro:
While riding to work today I ran the test suite on trunk. The following
tests failed due to lack of network connectivity:
test_socket
test_socket_ssl
test_ssl
test_urllib2
These tests should probably either require -u network or should
Skip Montanaro added the comment:
duplicate of 1659
--
resolution: -> duplicate
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Skip Montanaro added the comment:
I have no idea, but you can close this as far as I'm concerned.
Skip
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Changes by Skip Montanaro:
--
nosy: -skip.montanaro
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue602345>
___
Python-bugs-list mailing list
Skip Montanaro added the comment:
Do you have an example which doesn't require a login? Failing that,
can you tell us how to get the requisite login?
Skip
--
nosy: +skip.montanaro
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Skip Montanaro added the comment:
This is an easy patch, but I'd like someone to at least verify it works
before checking it in... nudge, nudge, wink, wink...
--
keywords: +easy
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Skip Montanaro added the comment:
> it currently mentions test_socket_ssl and test_timeout explicitly
"it" being regrtest.py? This patch works for me. In what way is
regrtest's reference to test_socket_ssl (for example) a problem? All
I did for that test was tighten up t
Skip Montanaro added the comment:
I'd personally be kind of surprised if Barry had any thoughts on this.
Is there any reason this couldn't be pushed down into the C code and
replace the normal tuple output completely? In the absence of any
fieldnames you could just dream some up, like
201 - 300 of 838 matches
Mail list logo
