Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I think the workaround proposed in my email in this bug is sufficient.
Blindly letting associate work on python wrapped overridden objects such
that the underlying library doesn't call into the wrapper could con
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
the redundant asserts were removed. reclosing.
further discussion on signedness issues in the code base should take
place on the mailing list, future bugs or peps as appropriate.
--
status: open -&g
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I'm going to let the committed change bake in Python trunk for a beta
release or two before backporting it to release25-maint.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
fixed in trunk r63405
--
priority: -> normal
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://b
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
This seems like a useful addition and is easy enough.
Patch with tests and documentation attached. Unless I hear objections I
will commit it to trunk later this week.
Patch available for review here: http://codereview.appspot.co
New submission from Gregory P. Smith <[EMAIL PROTECTED]>:
Using Linux with BerkeleyDB 4.7.25 the bsddb/test/test_replication.py
test is very flaky. It alternately passes, raises an AssertionError
because of the timeout or gets a segmentation fault or bus error.
(side note: i u
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I believe Jesus wants to do this is such a way that bsddb.h and _bsddb.c
are a single code base with #ifdef's that compiles on 2.x and 3.x at once.
--
assignee: -> jcea
__
Tracker <
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Could you supply some real code in a test case and better describe the
environment needed to reproduce this? (what OS for the client and
server, 64bit, 32bit, mount options, etc).
--
nosy: +gregory.p.smith
priority: ->
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Yes, sounds like a bug. I'll fix it.
But should time.strftime allow a unicode format string as input in the
first place? For backwards compatibility I'd say yes. But.. Sane
output can not be guaranteed from time.strft
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Fixed in trunk r63617.
Fix issue2669: bsddb simple/legacy interface iteration silently fails
when database changes size during iteration.
It now behaves like a dictionary, the next attempt to get a value from
the iterator aft
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I believe that means we can close this issue here? If not, please reopen.
--
nosy: +gregory.p.smith
resolution: -> invalid
status: open -> closed
__
Tracker <[EMAIL PR
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2595>
__
___
Python-b
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
nosy: +gregory.p.smith
priority: -> high
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2523>
__
__
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
priority: -> release blocker
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2949>
__
___
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
resolution: -> invalid
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2455>
__
__
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Could you please create a test case for this as a patch to
Lib/test/test_httpservers.py?
thanks!
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
priority: -> normal
__
Tra
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
keywords: +patch
nosy: +gregory.p.smith
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
nosy: +gregory.p.smith
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2901>
__
_
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
keywords: +patch
nosy: +gregory.p.smith
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
fixed in release25-maint r63881.
--
resolution: -> accepted
status: open -> closed
versions: +Python 2.5
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
committed to trunk r63882 for inclusion in 2.6.
--
resolution: -> fixed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2871>
___
__
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Fixed in release25-maint r63883.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Fixed in release25-maint r63883.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Fixed in trunk (2.6) r63887.
--
assignee: gregory.p.smith ->
resolution: -> fixed
status: open -> closed
versions: -Python 2.6
___
Python tracker <[EMAIL PROTECTED]>
&l
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
nosy: +gregory.p.smith
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2862>
___
_
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
everyone seems to be in agreement that this patch is a bad idea. closing.
--
nosy: +gregory.p.smith
resolution: -> rejected
status: open -> closed
___
Python tracker <[EMAIL PR
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I agree with this patch and will commit it later this weekend if I hear
no objections. see the mailing list discussion.
--
assignee: christian.heimes -> gregory.p.smith
___
Pytho
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
versions: -Python 2.6
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2632>
___
_
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Test disabled on 64bit when using the supplied patch when forward
porting to 2.6 in trunk revision 64114.
--
assignee: -> gregory.p.smith
keywords: +64bit, easy, patch
nosy: +gregory.p.smith
priority: -> high
resol
New submission from Gregory P. Smith <[EMAIL PROTECTED]>:
Python 2.6a3+ (trunk:64150M, Jun 11 2008, 14:08:14)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
% ./python Lib/t
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
ah yes that is indeed the same problem. marking this one as a dup.
--
dependencies: +Thread local storage and PyGILState_* mucked up by os.fork()
resolution: -> duplicate
status: open
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
we need this in before 2.6 is released.
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
priority: high -> critical
___
Python tracker <[EMAIL PROTECTED]>
<h
New submission from Gregory P. Smith <[EMAIL PROTECTED]>:
Currently the threading module has loops in it such as
threading.Condition.wait's loop that attempts to acquire a lock in
non-blocking mode and if it fails, sleeps for a while and trys again.
(with exponential backoff of slee
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
committed to 2.6 trunk in r64753.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
committed to release25-maint in r64754.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10027/issue2620-gps01-patch.txt
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
here's an updated patch. It makes PyMem_NEW and PyMem_RESIZE macros
always do explicit an overflow check before doing the multiplication.
Uses of the the macros have been cleaned up in the couple places I
noticed that would lea
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Fixed as Amaury described in trunk r64756.
still needs backporting to release25-maint.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
lowering the priority on this back to normal as there is a workaround:
use close_fds=True.
I agree that this is messy, I'm not sure if we can really fix it or even
if we should.
Running lsof shows the /bin/cat processes on OS X
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
keywords: +easy
nosy: +gregory.p.smith
priority: -> normal
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
thanks. fixed in trunk r64758. i'm assuming that'll be merged into
py3k automagically.
--
resolution: -> accepted
versions: +Python 3.0 -Python 2.6
___
Python tracke
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
priority: -> normal
title: socket's OOB data management is broken on FreeBSD -> socket's OOB data
management is b
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
priority: -> normal
title: socket's SO_OOBINLINE option does not work on FreeBSD -> socket's
SO_OOBINLINE option does not
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
This also happens on Linux:
read -> x
Exception in thread Thread-1:
Traceback (most recent call last):
File "/home/greg/sandbox/python/trunk/Lib/threading.py", line 523, in
__bootstrap_inner
self.run()
File
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
p648 of Unix Network Programming third edition:
"4. If the process has set the SO_OOBINLINE socket option and then tries
to read the out-of-band data by specifying MSG_OOB, EINVAL is returned."
so it does not sound like
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
further reading reveals that this is the expected behavior.
p651 in 24.2: "select indicates an exception condition until the process
reads -beyond- the out of band data." ... "the solution is to only
select for a
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
A friend confirms that on NetBSD it matches the Linux behavior.
"read -> x" is printed before the exception.
also fwiw, my OS X version is 10.5.3.
IMNSHO not a python bug. open it with FreeBSD and Apple.
--
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
not a python issue. thanks for opening one with FreeBSD.
--
resolution: -> invalid
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
keywords: +easy
nosy: +gregory.p.smith
priority: -> normal
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Fixed in trunk r64767.
Needs backporting to release25-maint.
--
resolution: -> accepted
type: -> behavior
versions: +Python 2.5 -Python 2.6
___
Python tracker <[EMAIL PR
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> jcea
nosy: +jcea
priority: -> normal
type: -> crash
___
Python tracker <[EMAIL PROTECTED]>
<http://b
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
take a look at the patch being worked on in issue #3262.
--
nosy: +gregory.p.smith
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> janssen
priority: -> normal
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
superseder: -> eliminate recursion in pickling
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
dependencies: +pickle.py is limited by python's call stack
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
seems harmless enough. done in trunk r64769.
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
priority: -> low
resolution: -> fixed
status: open -> closed
___
Pyth
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
components: +Library (Lib) -Extension Modules
nosy: +gregory.p.smith
priority: -> normal
versions: +Python 2.6
___
Python tracker <[EMAIL PR
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
sounds like a good idea to add this. yay firefox 3. i'll review it.
--
assignee: -> gregory.p.smith
components: +Library (Lib)
nosy: +gregory.p.smith
priority: -> normal
type: -> feature request
v
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
components: +Interpreter Core, Library (Lib)
nosy: +gregory.p.smith
priority: -> normal
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
components: +Extension Modules
nosy: +gregory.p.smith
priority: -> high
type: -> behavior
___
Python tracker <[EMAIL PROTECTED]>
<http://b
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
fixed in trunk r64771.
(and indeed the previous behavior was buggy in the extreemly rare event
that someone ran a https server on port 80 the :80 should have been
supplied).
--
assignee: -> gregory.p.smith
keywords: +
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> teoliphant
nosy: +gregory.p.smith
priority: -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
keywords: +patch
nosy: +gregory.p.smith
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
i'll come up with something for the documentation on this.
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
resolution: -> accepted
type: -> behavior
___
Py
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
fyi - To fix issue #2113 I added handling of a select.error errno.EINTR
being raised during the select.select call in r64756.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
assignee: -> gregory.p.smith
nosy: +gregory.p.smith
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pyth
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
The existing fork-and-thread4.patch doesn't actually reset
_active_limbo_lock. Its missing a "global _active_limbo_lock" statement
in the threading._after_fork() function.
___
P
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
and a few more bugs. a new patch is attached. With this applied,
pitrou's fork_threading.py bug demonstration script finally does the
right thing.
test_threading, including the new deadlock tests, and
test_multiprocessin
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10855/fork-and-thread.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10859/fork-and-thread2.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10869/fork-and-thread3.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10872/fork-and-thread4.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I still don't like the _after_fork() implementation. Its O(n) where n
== number of threads the parent process had.
Very wasteful when the fork() was done in the most common case of being
followed by an exec and calling os._
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
% ./python.exe -mtimeit 'isinstance(3, int)'
100 loops, best of 3: 0.269 usec per loop
% ../release25-maint/python.exe -mtimeit 'isinstance(3, int)'100
loops, best of 3: 0.335 usec per loop
So I'd sa
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
speedup of this patch confirmed. Also, it triggers the bugs mentioned
that have their own issues open. Once #2542 is fixed this should be
looked at again.
Its a big performance regression in 2.6 over 2.5 if we don't get this
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I am unable to reproduce this (using release24-maint on OS X 10.4). the
script I used is attached.
Does this script fail for you? If not, please upload something that fails.
--
nosy: +gregory.p.smith
Added file
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I added a Misc/NEWS note for this in r65057.
This is a good candidate for backporting to release25-maint.
To answer Antoine Pitrou's question about using the old ident vs the new
_get_ident(). I don't know if the for
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Jesse: thanks for doing the py3k merge.
Antoine: yeah it might be safer to use _get_ident() but since the
len(_active) == 1 assert is not firing we're probably fine as is.
A change to this that I was considering making to th
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
python 2.6b1+, bdb 4.7.25 on x86 ubuntu linux.
% ../../../../python/trunk/python bsddb3/tests/test_replication.py -v
test01_basic_replication (__main__.DBReplicationManager) ... zsh:
segmentation fault ../../../../python/trunk/
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
(that last comment was using pybsddb svn r529)
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
hmm. nevermind.
those last results clearly used the wrong bsddb library.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Okay, now i've run the correct test suite on the correct modules with
pybsddb r530:
The problems still happen. Sometimes it passes. Other times it raises
an assertion error.
test01_basic_replication DBReplicationManger e
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
i believe this patch will fix it. but i don't have a windows build
environment setup yet to even try it.
Exposing pointers to data structures as a number to Python is very gross
to begin with. It'd be safer to define a t
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
diff up for review on http://codereview.appspot.com/2599
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
Added file:
http://bugs.python.org/file10951/windows-amd64-subprocess-handle-gps02.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
Removed file:
http://bugs.python.org/file10950/windows-amd64-subprocess-handle-gps01.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
fixed in trunk r65151 (in theory).
I don't have amd64 to test with.
Roger, would you please test an AMD64 build from that revision or later
to confirm that it is fixed?
Once confirmed, this should be backported to rele
Changes by Gregory P. Smith <[EMAIL PROTECTED]>:
--
versions: -Python 2.6
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3120>
___
_
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
i believe this is fixed by the two changes mentioned above, i was
waiting for fbvortex to confirm the fix on his 64-bit OpenBSD system.
these changes need backporting to release25-maint.
--
status: pending -> open
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
using a python trunk optimized (non-debug) build and pybsddb r530:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Berkeley DB 4.7.25: (May 15, 2008)
bsddb.db.version(): (4, 7, 25)
bsddb.db.__ver
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Commited to trunk. r65182.
This still needs backporting to release25-maint. (and release24-maint
if anyone is maintaining that)
--
keywords: +patch
versions: +Python 3.0 -Pyth
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Fixed in trunk r65459. release25-maint r65460.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
fixed in release25-maint r65461. already merged into py3k from trunk.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
committed to release25-maint as r65466. if testing on 64bit openbsd or
similar reveals that this is not fixed, please reopen the bug.
--
status: open -> closed
___
Python tracke
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
See the documentation update in trunk r65469. It adds warnings about
both common pipe related pitfalls discussed in this bug.
--
resolution: accepted -> fixed
status: open -> closed
__
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
I tried closing -all- of the handles listed here (the std ones used as
input to _get_handles and the pipe read/write ones returned) on an
OSError during CreateProcess but the problem still occurs for me using
the test code in ms
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
fixed in release25-maint r65475.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Gregory P. Smith <[EMAIL PROTECTED]> added the comment:
Thanks. I've looked over your code. The logic looks good, however I'd
like to propose a better design and that this not be included in 2.6.
Instead of putting this functionality in the MozCookieJar class, it
shoul
301 - 400 of 3274 matches
Mail list logo
