Jesse Noller jnol...@gmail.com added the comment:
We have to add the BSD header and maintain the copyright clause on all of the
multiprocessing files. Apologies for the delay
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Changes by Jesse Noller jnol...@gmail.com:
--
nosy: +asksol
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10527
___
___
Python-bugs-list mailing
Changes by Jesse Noller jnol...@gmail.com:
--
nosy: +jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5725
___
___
Python-bugs-list mailing
Jesse Noller jnol...@gmail.com added the comment:
Adding, or moving, to SYSV semaphores is very low on the list of things to do.
If someone were to provide a patch, I'm sure we could consider it.
--
___
Python tracker rep...@bugs.python.org
http
Jesse Noller jnol...@gmail.com added the comment:
On Tue, Jan 18, 2011 at 6:23 PM, Brian Thorne rep...@bugs.python.org wrote:
Brian Thorne hardb...@gmail.com added the comment:
With the example script attached I see the exception every time. On Ubuntu
10.10 with Python 2.6
Since
Jesse Noller jnol...@gmail.com added the comment:
I'm fine with that tweak antoine
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10845
Jesse Noller jnol...@gmail.com added the comment:
Yeah, despite what the RFC says, the most common usage is in web clients, and
stuffing it in the email module won't be obvious to 95% of the population I
think, unless that's where the implementation lives, but we can add a doc stub
Jesse Noller jnol...@gmail.com added the comment:
This is on my wish list; but I have not had time to do it. Patch welcome.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8713
Jesse Noller jnol...@gmail.com added the comment:
I pretty much agree with (b) an argument - your gut instinct is correct -
there's a long standing thread in python-dev which pretty much solidified my
thinking about whether or not we need this (we do).
Any patch has to be backwards
Jesse Noller jnol...@gmail.com added the comment:
No - I don't know of anything which would trigger this in 3.1 off the top of my
head. The performance degradation is pretty worrisome
--
___
Python tracker rep...@bugs.python.org
http
Jesse Noller jnol...@gmail.com added the comment:
the patch looks good to me - unless someone beats me to it, I'm going to commit
it shortly to fix 2.7
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9144
Jesse Noller jnol...@gmail.com added the comment:
Pushed it in r82489 - worked for me on Linux and OS/X. Please let me know if
anything else comes up.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Jesse Noller jnol...@gmail.com added the comment:
Greg - what platform?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4106
___
___
Python-bugs
Jesse Noller jnol...@gmail.com added the comment:
Greg - this is actually a different exception then the original bug report;
could you please file a new issue with the information you've provided? I'm
going to need to find a 64bit ubuntu box as I don't have one right now
Jesse Noller jnol...@gmail.com added the comment:
Thanks greg; so this affects 2.6 as well (not using the backport at all)
--
assignee: - jnoller
nosy: +jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9207
Changes by Jesse Noller jnol...@gmail.com:
--
title: multiprocessing occasionally spits out exception during shutdown -
multiprocessing occasionally spits out exception during shutdown
(_handle_workers)
___
Python tracker rep...@bugs.python.org
Jesse Noller jnol...@gmail.com added the comment:
Oh, you mean the backport from google code?
The person who stepped up to maintain that has not refreshed that in some time.
I need to decide what to do with it long term. I'm pretty sure it's badly out
of date
Jesse Noller jnol...@gmail.com added the comment:
Wait - so, you are pulling svn trunk, compiling and running your test with the
built python executable? I'm not following the multiprocessing-from-trunk
distinction unless you're picking the module out of the tree / compiling
Jesse Noller jnol...@gmail.com added the comment:
Alright, I'm fighting ubuntu 64 bit in my vmware install right now, I'll see if
I can get it up and running.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9207
Jesse Noller jnol...@gmail.com added the comment:
Yes; the copyright has to stay; but the license data can leave afaik.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9162
Jesse Noller jnol...@gmail.com added the comment:
I can confirm with a clean ubuntu 64 install, with a clean checkout of
release27 that it explodes with that exception, while the stock 2.6.5 does not.
--
___
Python tracker rep...@bugs.python.org
Jesse Noller jnol...@gmail.com added the comment:
It does not seem to appear on OS/X 10.6.4 - so the only question is does this
show up on Ubuntu 32bit
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9207
Jesse Noller jnol...@gmail.com added the comment:
Correction; it can and does happen on OS/X. So, this is not a platform specific
bug.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9207
Jesse Noller jnol...@gmail.com added the comment:
Greg, can you comment out line 272 in Lib/multiprocessing/pool.py and tell me
if you can reproduce?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9207
Jesse Noller jnol...@gmail.com added the comment:
I'm not sure if there would still be the possibility; the thing which worries
me is the debug() function vanishing on us - something not good is happening on
interpreter shutdown.
--
___
Python
Jesse Noller jnol...@gmail.com added the comment:
Hi Stefan - I'm familiar with the license/etc of the original module. This bug
isn't urgent; I shot a quick email to the PSF's secretary Pat to confirm we
have a contributor agreement however
Jesse Noller jnol...@gmail.com added the comment:
Egad No! I gotcha. I'll find out what the deal with the contrib. agreement is.
Pretty sure we had to wait on it when we brought it in.
--
___
Python tracker rep...@bugs.python.org
http
Jesse Noller jnol...@gmail.com added the comment:
Greg - yeah. it's the same problem.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9207
Jesse Noller jnol...@gmail.com added the comment:
Talking with Brett; the fix should be as simple as keeping a reference to the
debug function which we have in the imports. During interpreter shutdown, the
sys.modules is iterated and each module replaced with None. Since the
_handle_workers
Jesse Noller jnol...@gmail.com added the comment:
thanks greg; I'm going to take a look and think about this. I'd like to resolve
bug 9207 first though
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9205
Changes by Jesse Noller jnol...@gmail.com:
--
assignee: - jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9205
___
___
Python-bugs-list
Jesse Noller jnol...@gmail.com added the comment:
Ugh. I'm going to have to think about the cleanest way of handling this case of
functions vanishing from us since this is going to be more widespread inside
the code. Suggestions welcome
Jesse Noller jnol...@gmail.com added the comment:
A+ for creativity; I wouldn't have thought of that ;)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9205
Jesse Noller jnol...@gmail.com added the comment:
Thank you for doing that footwork Greg, it means a lot to me. I'm leaning
towards the patch to swallow the errors - I just wanted to ponder it just a
tiny bit longer before I pull the trigger
Jesse Noller jnol...@gmail.com added the comment:
Greg - I asked Ask to take a look - his celery package is a huge consumer of
multiprocessing, and so I tend to run things past him as well.
That said - to both of you - the fundamental problem the shutdown patch is
trying to scratch
Changes by Jesse Noller jnol...@gmail.com:
--
assignee: - jnoller
nosy: +gdb
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9244
___
___
Python
Jesse Noller jnol...@gmail.com added the comment:
Passing the references seems to be a losing game; for _handle_workers - we
only need 1 function (debug) - for others (say _join_exited_workers), we need
references to reversed/range/len.
A possible alternative is to make those threads non
Jesse Noller jnol...@gmail.com added the comment:
You two are bigger users of this then I currently am (the curse/blessing of
switching jobs), which is why I've let you hash it out.
Let me point out: my goal is to deal with errors in a way which does not cause
a total crash, a lockup
Jesse Noller jnol...@gmail.com added the comment:
(sorry, I thought I had replied to your comment when I hadn't!) I think we can
get away with a new optional kwarg.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9205
Jesse Noller jnol...@gmail.com added the comment:
@Mark Yeah - I'm the current multiprocessing maintainer. If I fix it, I'll just
commit it :) I filed this as a to do against myself.
--
___
Python tracker rep...@bugs.python.org
http
Jesse Noller jnol...@gmail.com added the comment:
@ray - you probably don't have the dcon binary on your path. bug.py calls a
subprocess call.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9400
Jesse Noller jnol...@gmail.com added the comment:
The backport of multiprocessing is currently stale; and there are a few bugs in
the tracker assigned to christian or myself in regards to it. If it's not too
much trouble, I'd leave this one alone until the exact future of the backport
can
Jesse Noller jnol...@gmail.com added the comment:
The relative imports have been more of a pain then they've helped. I'm fine
with nuking them so long as the test suite passes.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Jesse Noller jnol...@gmail.com added the comment:
Mark - did you observe the behavior in the Op? He's not stating the the code
snippet runs fine, but that the second run at the same time on windows to cause
a conflict. We need to show that either running it twice, at the same time
against
Jesse Noller jnol...@gmail.com added the comment:
I don't know that it's unreasonable to send that much data, but it would
certainly be slow, and I would not recommend it. Therefore, this is still on
the list for when I have time
--
___
Python
Jesse Noller jnol...@gmail.com added the comment:
I agree with Antoine
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9586
___
___
Python-bugs
Jesse Noller jnol...@gmail.com added the comment:
Florent - Are you running the script from Freek on the buildbots, or are you
just updating this bugs with other run failures? I'm having a really hard time
separating things.
--
___
Python tracker
Jesse Noller jnol...@gmail.com added the comment:
Is this intermittent, or consistently failing? Updating it with more buildbot
failures doesn't help.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8428
Jesse Noller jnol...@gmail.com added the comment:
looks fine mark
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9586
___
___
Python-bugs-list
Jesse Noller jnol...@gmail.com added the comment:
Thanks Freek - we're actually discussing some stuff like this in issue9205 as
well
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9592
Jesse Noller jnol...@gmail.com added the comment:
Nice.
--
nosy: +jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9663
___
___
Python-bugs
Jesse Noller jnol...@gmail.com added the comment:
If we keep that behavior, the real problem here is that the
result handler hangs if the process that reserved a job is gone, which is
going to be handled
by #9205. Should we mark it as a duplicate?
I would tend to agree with your assessment
Jesse Noller jnol...@gmail.com added the comment:
Calling it stupid doesn't incentivize me to help you, or fix it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9851
Jesse Noller jnol...@gmail.com added the comment:
On Thu, Sep 16, 2010 at 8:15 AM, Michael Fladischer
rep...@bugs.python.org wrote:
Michael Fladischer mich...@fladi.at added the comment:
Is there any timeline on when this will be fixed? It's currently blocking
work on a python-related
Jesse Noller jnol...@gmail.com added the comment:
Duplicate; 9897
--
resolution: - duplicate
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9851
Jesse Noller jnol...@gmail.com added the comment:
hume; filing this again doesn't help. I closed issue 9851 as a duplicate of
this for you.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9897
Jesse Noller jnol...@gmail.com added the comment:
I can not, for the life of me, remember why ThreadPool is there, except as a
fallback. It's also not part of the documented interface as well. Additionally,
in Python 3 we now have futures
Jesse Noller jnol...@gmail.com added the comment:
I doubt I, or Ask will have the time to rewrite the entire multiprocessing test
suite right now to work around the change Antoine.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Jesse Noller jnol...@gmail.com added the comment:
Sridhar can you confirm if this is still a problem on 3.2?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6645
Changes by Jesse Noller jnol...@gmail.com:
--
assignee: jnoller - nobody
keywords: +easy
nosy: +nobody
priority: normal - low
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6269
Jesse Noller jnol...@gmail.com added the comment:
On Mon, Oct 25, 2010 at 10:17 AM, Antoine Pitrou rep...@bugs.python.org wrote:
Well, I'm not asking anyone to rewrite the entire multiprocessing test suite;
and, besides, I've provided a patch myself to improve it in that respect
Jesse Noller jnol...@gmail.com added the comment:
Closing per Sridhar
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6645
Jesse Noller jnol...@gmail.com added the comment:
Fine w/ committing this Ask.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9244
Jesse Noller jnol...@gmail.com added the comment:
Fine w/ committing this Ask.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7707
Jesse Noller jnol...@gmail.com added the comment:
Fine w/ committing this Ask as-is ask. You are correct in the original intent
of the code.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8028
Jesse Noller jnol...@gmail.com added the comment:
Can you please expand on deeply different?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8028
Jesse Noller [EMAIL PROTECTED] added the comment:
Bumping up _ I'll need help with a patch
--
priority: - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3770
Jesse Noller [EMAIL PROTECTED] added the comment:
The patch looks fine to me Ben, if you want to apply it.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3927
Jesse Noller [EMAIL PROTECTED] added the comment:
I've been thinking about this - Right now, having a working mp.synchronize
module, and thread support is key to package currently. For 2.6 - it's
really too late to try to mock up a working mp.synchronize module, or
significantly change
Jesse Noller [EMAIL PROTECTED] added the comment:
Hows this error look:
import multiprocessing
Traceback (most recent call last):
File stdin, line 1, in module
File /Users/jesse/open_source/subversion/python-
trunk/Lib/multiprocessing/__init__.py, line 178, in module
function, see
Jesse Noller [EMAIL PROTECTED] added the comment:
Is thereforce an actual word? Otherwise it looks fine to me.
Yeah, I caught that. Rather than disable the entire package, which
would be frustrating to many - I've changed it to only disable
mp.synchronize for now, patch is pending my final
Jesse Noller [EMAIL PROTECTED] added the comment:
Here's a patch, works on my machine. Please review it and make sure it
satisfies what we've spoken about.
--
keywords: +needs review, patch
Added file: http://bugs.python.org/file11656/issue3770.diff
Jesse Noller [EMAIL PROTECTED] added the comment:
On Sep 29, 2008, at 6:36 PM, Damien Miller [EMAIL PROTECTED]
wrote:
Damien Miller [EMAIL PROTECTED] added the comment:
I can confirm that the patch works on OpenBSD -current. Only one nit:
Does this line in Lib/test
Changes by Jesse Noller [EMAIL PROTECTED]:
--
assignee: georg.brandl - jnoller
nosy: +jnoller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4012
Jesse Noller [EMAIL PROTECTED] added the comment:
Which examples are you talking about Georg?
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4012
___
___
Python
Jesse Noller [EMAIL PROTECTED] added the comment:
Also, several things which are properties are still referred to as methods
and include the () chars for the call
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4012
Jesse Noller [EMAIL PROTECTED] added the comment:
Ok, let me take a look at that
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4012
___
___
Python-bugs-list
Changes by Jesse Noller [EMAIL PROTECTED]:
--
assignee: - jnoller
nosy: +jnoller
priority: - normal
versions: +Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4028
Changes by Jesse Noller [EMAIL PROTECTED]:
--
assignee: - jnoller
nosy: +jnoller
priority: - normal
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3876
Changes by Jesse Noller [EMAIL PROTECTED]:
--
title: multiprocessing does not compile on *BSD and potentialy other systems -
multiprocessing does not compile on systems which do not define sem_timedwait
___
Python tracker [EMAIL PROTECTED]
http
Jesse Noller [EMAIL PROTECTED] added the comment:
fix_up_logger doesn't exist in the port, but is used in the mp_distributing.py
example
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4012
Jesse Noller [EMAIL PROTECTED] added the comment:
Are you suggesting we apply this to the 2.6/2.7 branch?
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4208
Changes by Jesse Noller [EMAIL PROTECTED]:
--
nosy: +jnoller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4204
___
___
Python-bugs-list mailing list
Jesse Noller [EMAIL PROTECTED] added the comment:
Please see issue3770 for details on the multiprocessing library, SEM_OPEN
and freebsd. The short answer is that FreeBSD support for MP is not
available.
___
Python tracker [EMAIL PROTECTED]
http
Jesse Noller [EMAIL PROTECTED] added the comment:
The 3.0 doc/example issue is in issue 3256
I plan on fixing all the doc/example issue this/next week.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4449
Jesse Noller [EMAIL PROTECTED] added the comment:
Yes, I have a pending patch. I'll see if I can steal some time today
to check it in.
On Fri, Nov 28, 2008 at 9:36 AM, Christian Heimes
[EMAIL PROTECTED] wrote:
Christian Heimes [EMAIL PROTECTED] added the comment:
Are you able to fix
Jesse Noller [EMAIL PROTECTED] added the comment:
As ben mentioned, this is already fixed in core. See issue 1683 - this is
only a problem when running in 2.5/2.4
--
resolution: - duplicate
status: open - closed
___
Python tracker [EMAIL PROTECTED
Changes by Jesse Noller [EMAIL PROTECTED]:
--
nosy: +jnoller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1683
___
___
Python-bugs-list mailing list
Jesse Noller [EMAIL PROTECTED] added the comment:
Hmm, we should actually rename mp.Queue to mp.queue at one point
--
nosy: +jnoller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4450
Jesse Noller [EMAIL PROTECTED] added the comment:
I guess you just 2to3'ed the examples
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4449
___
___
Python-bugs
Jesse Noller [EMAIL PROTECTED] added the comment:
Added in r67419 on trunk, merged to py3k and 2.6.1
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4193
Jesse Noller [EMAIL PROTECTED] added the comment:
Added the mp.managers shared queue example, fixed the docs in r67419 on
trunk. merged to py3k and 2.6.1 maint
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http
Jesse Noller [EMAIL PROTECTED] added the comment:
Warning added for georg's issue, all doc errors fixed on trunk, py3k and
2.6.1 maint. see r67419
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http
Jesse Noller [EMAIL PROTECTED] added the comment:
Fixed, trunk r67423
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4238
Jesse Noller [EMAIL PROTECTED] added the comment:
This is not a doc bug - in actuality, the mp_benchmarks.py example is
exposing an assertion error in sharedctypes.py.
The doc-related bugs Christian and I spoke about have been fixed, however
the main issue for this (the assertion error
Jesse Noller [EMAIL PROTECTED] added the comment:
2.6.0 shipped with the assertion error. Unfortunately, I'm tapped out at
the day job right now, so I won't have a fix prepped and tested in time.
--
priority: release blocker - deferred blocker
Jesse Noller [EMAIL PROTECTED] added the comment:
+1 on Amaury's patch, however I wouldn't change the assert right now -
Christian's suggestion does make sense to change globally post 3.0
Amaury, do you want to submit it?
___
Python tracker [EMAIL PROTECTED
Jesse Noller [EMAIL PROTECTED] added the comment:
Ah, I see what you're talking about David. Good catch. It wouldn't make
sense to run the apply() in all of the workers, as apply() is a single
function(...) call. map() however is done in parallel amongst all workers
Changes by Jesse Noller [EMAIL PROTECTED]:
--
resolution: - duplicate
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3206
Jesse Noller [EMAIL PROTECTED] added the comment:
Dupe, issue4449
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3206
___
___
Python-bugs-list mailing list
1 - 100 of 532 matches
Mail list logo