On Mon, Jul 22, 2013 at 6:36 PM, Victor Stinner
wrote:
> Could you please keep the comment "# A symlink can never be a mount point" ?
> It is useful. (I didn't know that, I'm not a windows developer.)
I don't think that's specific to Windows, but I added it back in d6213012d87b.
_
On Wed, Jul 24, 2013 at 10:56 AM, Lennart Regebro wrote:
> On Wed, Jul 24, 2013 at 3:54 PM, Lennart Regebro wrote:
>> On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda wrote:
>>> - Should we point /usr/bin/python to Python 3 when we make the move?
>>
>> No.
>
> To be more explicit. I think it's
On Thu, Jul 25, 2013 at 9:37 AM, Christian Heimes wrote:
> Am 25.07.2013 16:29, schrieb Eli Bendersky:
>> Hi all,
>>
>> I've been looking for a Github mirror for Python, and found two:
>>
>> * https://github.com/python-git/python has a lot of forks/watches/starts
>> but seems to be very out of dat
On Thu, Aug 1, 2013 at 3:36 PM, Terry Reedy wrote:
> On 8/1/2013 11:03 AM, Alexander Shorin wrote:
>>
>> ...and, if so, why lambda's?(: Without backward compatibility point I
>> see that they are getting "unofficially" deprecated and their usage is
>> dishonoured.
>
>
> Please stop both the top-po
On Thu, Aug 1, 2013 at 3:44 PM, Brian Curtin wrote:
> On Thu, Aug 1, 2013 at 3:36 PM, Terry Reedy wrote:
>> On 8/1/2013 11:03 AM, Alexander Shorin wrote:
>>>
>>> ...and, if so, why lambda's?(: Without backward compatibility point I
>>> see that they
On Fri, Sep 6, 2013 at 9:51 AM, Ethan Furman wrote:
> I recently committed a fix for unicodeobject.c so that the %d, %i, and %u
> format specifiers always output values (otherwise, in subclasses, the str()
> was used instead).
>
> Should this be fixed in 3.3 as well?
>
> What guidelines determine
On Sat, Oct 12, 2013 at 3:17 PM, Serhiy Storchaka wrote:
> 12.10.13 22:56, Antoine Pitrou написав(ла):
>
>> On Sat, 12 Oct 2013 21:19:16 +0200
>> Georg Brandl wrote:
>>>
>>> Am 12.10.2013 20:20, schrieb Serhiy Storchaka:
12.10.13 21:04, Georg Brandl написав(ла):
>
> in light of
___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brian%40python.org
>
On Thu, Mar 23, 2017 at 12:19 PM, Barry Warsaw wrote:
> On Mar 23, 2017, at 09:41 AM, Victor Stinner wrote:
>
>>Can we pick an official date?
>
> Benjamin should pick the date and update PEP 373.
Not to start a bikeshed (calendarshed?), but how about 8 February
2020, or 2/8 as some in the US woul
On Wed, Sep 6, 2017 at 10:46 AM, Guido van Rossum wrote:
> IIRC they indeed insinuate debug() into the builtins. My suggestion is
> also breakpoint().
>
I'm also a bigger fan of the `breakpoint` name. `debug` as a name is
already pretty widely used, plus breakpoint is more specific in naming
wha
On Sun, Jan 30, 2022 at 8:42 AM Mats Wichmann wrote:
> On 1/30/22 04:45, Inada Naoki wrote:
> > On Sun, Jan 30, 2022 at 7:37 PM Irit Katriel
> wrote:
>
> > Some people may do "approval without review" to make their "Profile"
> > page richer, because GitHub counts it as a contribution.
> > Creati
are 10% each.
On Mon, Jan 31, 2022 at 9:40 AM Guido van Rossum wrote:
> Where does it say that a review gives you points? The GitHub blog post I
> saw about the subject only mentions commits.
>
> On Mon, Jan 31, 2022 at 8:16 AM Brian Curtin wrote:
>
>> On Sun, Jan 30, 2022 at
> This whole thread would be an excellent justification for following 3.9
> with 4.0. It's as near as we ever want to get to a breaking change, and a
> major version number would indicate the need to review. If increasing
> strictness of escape code interpretation in string literals is the only
> i
Eric V. Smith wrote:
> Hopefully the warnings in 3.9 would be more visible that what we saw in
> 3.7, so that library authors can take notice and do something about it
> before 3.10 rolls around.
> Eric
Apologies for the ~double-post on the thread, but: the SymPy team has figured
out the right
Nathaniel Smith wrote:
> Unfortunately, their solution isn't a pytest incantation, it's a
> separate 'compileall' invocation they run on their source tree. I'm
> not sure how you'd convert this into a pytest feature, because I don't
> think pytest always know which parts of your code are your code
Citing from the current (19 Aug 2019) version of this PR
(https://github.com/python/devguide/pull/525/files#diff-50cb76bbe8ae3fcd4170dc6e8d9d6b3fR225-R226):
> Before using any Sphinx roles, ensure that a corresponding entry exists
> within the documentation.
At the risk of crass self-promotion,
it's getting better?
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/
I've appreciated Anthony Sottile's flake8-2020 plugin
(https://pypi.org/project/flake8-2020/), which adds checks for a variety of
misuses of sys.version and sys.version_info that would lead to breakage on a
Python 4.0, and/or 10.0, in addition to Python 3.10.
On Tue, Apr 21, 2020 at 7:31 AM Larry Hastings wrote:
> On 4/20/20 8:06 AM, Benjamin Peterson wrote:
>
> I'm eudaemonic to announce the immediate availability of Python 2.7.18. [...]
> Over all those years, CPython's core developers and contributors sedulously
> applied bug fixes to the 2.7 bra
Well done Larry! so long and thanks for all the Pythons.
--
Brian Ray
brian-ray.me
<https://brian-ray.me/?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
ᐧ
___
Python-Dev mail
Hey Team,
Has this workgroup started yet? If not, can I help get it going, or if so,
is there a mailing list or place where things are happening?
Brian Curtin
On Sun, Aug 9, 2020 at 12:58 Carol Willing wrote:
> Hi folks,
>
> Thanks for the interest. I apologize for the delay in get
ould you explain why
_RawIOBase.close() calling self.flush() is useful?
Cheers,
Brian
Antoine Pitrou wrote:
Hi!
sweetapp.com> writes:
class _RawIOBase(_FileIO):
FileIO is a subclass of _RawIOBase, not the reverse:
issubclass(_io._RawIOBase, _io.FileIO)
False
issubclass(_io.FileIO, _io._RawIOBase)
Antoine Pitrou wrote:
Brian Quinlan sweetapp.com> writes:
I don't see why this is helpful. Could you explain why
_RawIOBase.close() calling self.flush() is useful?
I could not explain it for sure since I didn't write the Python version.
I suppose it's so that people who o
James Y Knight wrote:
On Apr 5, 2009, at 6:29 AM, Antoine Pitrou wrote:
Brian Quinlan sweetapp.com> writes:
I don't see why this is helpful. Could you explain why
_RawIOBase.close() calling self.flush() is useful?
I could not explain it for sure since I didn't write the Pyth
Nick Coghlan wrote:
Brian Quinlan wrote:
- you need the cooperation of your subclasses i.e. they must call
super().flush() in .flush() to get correct close behavior (and this
represents a backwards-incompatible semantic change)
Are you sure about that? Going by the current _pyio semantics
close()
# IOBase._close()
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Tue, Jan 5, 2010 at 10:10, Juan Fernando Herrera J. wrote:
> How about a new python 3 release with (possibly partial) backwards
> compatibility with 2.6? I'm a big 3 fan, but I'm dismayed at the way major
> software hasn't been ported to it. I'm eager to use 3, but paradoxically,
> the 3 releas
eir patches have been committed and the issue remains
open. What is the best course of action there? I'd just go ahead and close
the issue myself but I don't have tracker privileges.
I'm willing to help out with another Daniel Diniz-esque triage sweep if that
would help.
Brian
On Wed, Jan 6, 2010 at 19:28, Brett Cannon wrote:
>
>
> On Wed, Jan 6, 2010 at 17:22, R. David Murray wrote:
>
>>
>> On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
>> > On Wed, Jan 6, 2010 at 06:57, Brian Curtin
>> wrote:
>> > &
a black hole?
Food for thought: according to the last tracker summary, there are over 1000
open issues with a patch, and issues stay open an average of 700 days
(median 450).
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
On Tue, Jan 12, 2010 at 04:20, Antoine Pitrou wrote:
> Le Mon, 11 Jan 2010 19:57:46 -0600, Brian Curtin a écrit :
> >
> > For example, there are currently over
> > 1500 open issues with no stage set, some of which seemingly haven't been
> > read by anyone at al
On Tue, Jan 19, 2010 at 21:43, David Lyon wrote:
>
> Being honest, if wonderful libraries like Sphinx and Mercurial
> and Git and BZR can't make it into the stdlib, then there is
> no hope for even newer code to get in there.
>
I'm not entirely sure I see why the inclusion of a SCM into the stdl
On Tue, Feb 9, 2010 at 06:45, anatoly techtonik wrote:
> On Tue, Feb 9, 2010 at 12:57 PM, Antoine Pitrou
> wrote:
> > Le Tue, 09 Feb 2010 12:16:15 +0200, anatoly techtonik a écrit :
> >>
> >> I've noticed a couple of issues that 100% crash Python 2.6.4 like this
> >> one - http://bugs.python.org
On Tue, Feb 9, 2010 at 12:29, Olemis Lang wrote:
> On Tue, Feb 9, 2010 at 11:42 AM, Michael Foord
> wrote:
> > I'm pretty sure I can introduce setUpClass and setUpModule without
> breaking
> > compatibility with existing unittest extensions or backwards
> compatibility
> > issues
>
> Is it possi
On Fri, Feb 19, 2010 at 08:40, Sjoerd Mullender wrote:
> On 2010-02-19 14:10, Guido van Rossum wrote:
> > Isn't mhlib itself deprecated? (It's gone in Py3k.)
>
> I wouldn't like that, but it is beside my point. If a module is
> deprecated, then it should not be used in released code.
> If mhlib
On Wed, Feb 24, 2010 at 18:48, Antoine Pitrou wrote:
> Le Wed, 24 Feb 2010 12:13:10 +, Florent Xicluna a écrit :
> > Hello,
> >
> > I am a semi-regular contributor for Python: I have contributed many
> > patches since end of last year, some of them were reviewed by Antoine.
>
> Semi-regular i
n: %s' % (url,
future.exception()))
else:
print('%r page is %d bytes' % (url, len(future.result(
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Fri, Mar 5, 2010 at 12:51, Neal Becker wrote:
> I generally enjoy argparse, but one thing I find rather
> ugly and unpythonic.
>
>parser.add_argument ('--plot', action='store_true')
>
> Specifying the argument 'action' as a string is IMO ugly.
>
What else would you propose?
FWIW, this is
On 6 Mar 2010, at 03:21, Daniel Stutzbach wrote:
On Fri, Mar 5, 2010 at 12:03 AM, Brian Quinlan
wrote:
import futures
+1 on the idea, -1 on the name. It's too similar to "from
__future__ import ...".
Also, the PEP should probably link to the discussions on stdlib-s
, return_when=ALL_COMPLETED)``?
Hi Brett,
That recommendation was designed to make it easy to change the API
without breaking code.
I'd don't think that recommendation makes sense anymore any I'll
update the PEP.
Cheers,
Brian
On Thu, Mar 4, 2010 at 22:03, Brian Quinlan
wro
to propose the concurrent.futures name
or you can draft a more complete PEP that describes what other
functionality should live in the concurrent package.
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/
On 6 Mar 2010, at 09:54, Antoine Pitrou wrote:
Le Fri, 5 Mar 2010 17:03:02 +1100,
Brian Quinlan a écrit :
The PEP lives here:
http://python.org/dev/peps/pep-3148/
Ok, here is my take on it:
cancel()
Attempt to cancel the call. If the call is currently being executed
then it cannot be
do it, not necessarily directly copying
actual APIs or implementations. Certainly some of the Deferred API
naming has a rather, um, "twisted" vocabulary.)
Using twisted (or any other asynchronous I/O framework) forces you to
rewrite your I/O code. Futures do not.
Cheers,
Brian
On 7 Mar 2010, at 03:04, Phillip J. Eby wrote:
At 05:32 AM 3/6/2010, Brian Quinlan wrote:
Using twisted (or any other asynchronous I/O framework) forces you to
rewrite your I/O code. Futures do not.
Twisted's "Deferred" API has nothing to do with I/O.
I see, you just mean
without this patch, the deadlock test I am skipping in
the patch and the two that fail do so for a reason that does not make
sense to me.
I'll investigate but I don't have convenient access to a windows
machine.
Cheers,
Brian
___
Python-Dev ma
t want to continue if there is a failure.
In the example that you gave, if "proc3" raises an exception
immediately, you still wait for "proc1" and "proc2" to complete even
though you will end up discarding their results.
Cheers,
Brian
nates the unpleasant interpreter
shutdown/module globals interactions that have plagued a number of
stdlib systems that keep global state.
I'm not sure what you mean, could you clarify?
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@python.o
On 9 Mar 2010, at 03:21, Terry Reedy wrote:
On 3/6/2010 4:20 AM, Brian Quinlan wrote:
On 6 Mar 2010, at 03:21, Daniel Stutzbach wrote:
On Fri, Mar 5, 2010 at 12:03 AM, Brian Quinlan mailto:br...@sweetapp.com>> wrote:
import futures
+1 on the idea, -1 on the name. It's too
On 10 Mar 2010, at 23:32, Nick Coghlan wrote:
Brian Quinlan wrote:
Getting rid of the process-global state like this simplifies testing
(both testing of the executors themselves and of application code
which uses them). It also eliminates the unpleasant interpreter
shutdown/module globals
limited in size.
Should every thread/process exit when it finishes its job or should
there be a smarter collection strategy?
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubs
On Fri, Mar 19, 2010 at 03:09, anatoly techtonik wrote:
> I want to push some of my patches before 2.7 and use 5-1 rule for
> that, but I can't come up with any review workflow other than mailing
> status of my comments to the issues here. I can't mark issues in any
> way. How about giving users a
On Sat, Mar 20, 2010 at 11:02, Terry Reedy wrote:
> I did not receive the usual Friday tracker post on issues opened and closed
> during the past week.
> Did anyone else?
> I am reading via gmane.
>
> Terry Jan Reedy
>
I actually haven't seen that mail in a few weeks (subscribed to the list via
test patches
when they don't have direct access to Windows.
Brian Curtin
p.s. My contributor form in on file as of 2010-01-31.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscr
On Sat, Apr 10, 2010 at 10:51, Nick Coghlan wrote:
> The trunk's been frozen for a few days now, which is starting to cut
> into the window for new fixes between b1 and b2 (down to just under 3
> weeks, and that's only if b1 was ready for release today).
>
> Is work in train to address or documen
On Sat, Apr 10, 2010 at 13:37, Tim Golden wrote:
> On 10/04/2010 17:02, Brian Curtin wrote:
>
>> I contacted David Bolen for some details about the his buildbot because I
>> can't reproduce the failure on any Windows XP, Server 2003, or 7 box that
>> I
>> have,
On Wed, Apr 14, 2010 at 12:36, Steve Holden wrote:
> Paul Moore wrote:
> > On 14 April 2010 07:37, Paul Rudin wrote:
> >> "Martin v. Löwis" writes:
> >>
> >>> The major difference in the "do it yourself" attitude is that Mac user
> >>> get a compiler for free, as part of the operating system re
On Wed, Apr 14, 2010 at 14:03, "Martin v. Löwis" wrote:
> Paul Rudin wrote:
> > "Martin v. Löwis" writes:
> >
> >> The major difference in the "do it yourself" attitude is that Mac user
> >> get a compiler for free, as part of the operating system release,
> >> whereas for Windows, they have to
On Tue, Apr 13, 2010 at 14:43, David Bolen wrote:
> Brian Curtin writes:
>
> > The tests are run on a native Win32 build as compiled by VS2008. The
> > functionality is Win32 specific and wouldn't work on Cygwin, so the tests
> > are skipped there. I believe Cygwi
On Thu, Apr 15, 2010 at 03:20, anatoly techtonik wrote:
> On Tue, Apr 13, 2010 at 3:54 PM, Nick Coghlan wrote:
> >
> >>>I am surprised to see that the bug-tracker
> >>> doesn't have an OS classifier or ability to add
> >>> tags ? Since a number of issues reported seem to
>
> Just to r
) We do ask that requests are for
people who are active contributors and not just minor/occasional
participants.
"""
If this applies to you and you are interested, let me know.
Brian Curtin
___
Python-Dev mailing list
Python-Dev@python.org
know of no restrictions on what it's used for outside of
CPython.
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Mon, Apr 19, 2010 at 06:48, Steve Holden wrote:
> Antoine Pitrou wrote:
> > Le Fri, 16 Apr 2010 08:01:54 -0500, Brian Curtin a écrit :
> >> The recent threads on builds/installers for Mac and Windows reminded me
> >> of Steve Holden's push to get th
On Tue, Apr 20, 2010 at 14:42, Brett Cannon wrote:
> If you are a committer and are NOT subscribed to the python-committers
> mailing list (I believe this at least includes Giampaolo, JP, and Brian),
> then please either reply to this email with your preferred email address or
>
On Tue, Apr 27, 2010 at 09:22, Daniel Stutzbach <
dan...@stutzbachenterprises.com> wrote:
> May I have enhanced permissions on the bug tracker, so that I can perform
> the following tasks?
>
> - Assign issues to myself that I plan to write a patch for
> - Update the Stage to "patch review" after w
I've updated the PEP to include:
- completion callbacks (for interoperability with Twisted Deferreds)
- a pointer to the discussion on stdlig-sig
See:
http://svn.python.org/view/peps/trunk/pep-3148.txt?r1=78618&r2=80679
Rejected ideas:
- Having a registration system for executors
Not yet addres
The PEP is here:
http://www.python.org/dev/peps/pep-3148/
I think the PEP is ready for pronouncement, and the code is pretty
much ready for submission into py3k (I will have to make some minor
changes in the patch like changing the copyright assignment):
http://code.google.com/p/pythonfutures
Hey Mark,
This really isn't the time to propose changes.
The PEP has been discussed extensively on stdlib-sig and python-dev.
On May 21, 2010, at 9:29 PM, Mark Summerfield wrote:
On 2010-05-21, Brian Quinlan wrote:
The PEP is here:
http://www.python.org/dev/peps/pep-3148/
[snip]
Hi
On May 21, 2010, at 9:44 PM, John Arbash Meinel wrote:
Brian Quinlan wrote:
The PEP is here:
http://www.python.org/dev/peps/pep-3148/
I think the PEP is ready for pronouncement, and the code is pretty
much
ready for submission into py3k (I will have to make some minor
changes
in the
On May 21, 2010, at 9:47 PM, John Arbash Meinel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Quinlan wrote:
The PEP is here:
http://www.python.org/dev/peps/pep-3148/
I think the PEP is ready for pronouncement, and the code is pretty
much
ready for submission into py3k (I
On May 22, 2010, at 5:30 AM, Dj Gilcrease wrote:
On Fri, May 21, 2010 at 8:26 AM, Brian Quinlan
wrote:
Except that now isn't the time for that discussion. This PEP has
discussed
on-and-off for several months on both stdlib-sig and python-dev.
I think any time till the PEP is accept
On 22 May 2010, at 23:59, R. David Murray wrote:
On Sat, 22 May 2010 19:12:05 +1000, Brian Quinlan
wrote:
On May 22, 2010, at 5:30 AM, Dj Gilcrease wrote:
On Fri, May 21, 2010 at 8:26 AM, Brian Quinlan
wrote:
Except that now isn't the time for that discussion. This PEP has
discuss
Hey all,
Jesse, the designated pronouncer for this PEP, has decided to keep
discussion open for a few more days.
So fire away!
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On May 23, 2010, at 9:43 AM, Jeffrey Yasskin wrote:
I think the PEP's overall API is good to go.
On Sat, May 22, 2010 at 4:12 PM, Brian Quinlan
wrote:
On 22 May 2010, at 23:59, R. David Murray wrote:
If there is still discussion then perhaps the PEP isn't ready for
pronouncemen
On May 23, 2010, at 10:06 AM, Jeffrey Yasskin wrote:
On Sat, May 22, 2010 at 4:12 PM, Brian Quinlan
wrote:
Rename "executor" => "executer"
-1 for consistency with Java.
-1 pending an explanation of why "executer" is better
Rename "submit" to
On May 23, 2010, at 2:44 PM, Glyph Lefkowitz wrote:
On May 22, 2010, at 8:47 PM, Brian Quinlan wrote:
Jesse, the designated pronouncer for this PEP, has decided to keep
discussion open for a few more days.
So fire away!
As you wish!
I retract my request ;-)
The PEP should be
On May 23, 2010, at 7:15 PM, geremy condra wrote:
On Sun, May 23, 2010 at 2:37 AM, Brian Quinlan
wrote:
Finally, why isn't this just a module on PyPI? It doesn't seem
like there's
any particular benefit to making this a stdlib module and going
through the
whole PEP p
On May 23, 2010, at 7:54 PM, Lennart Regebro wrote:
On Sun, May 23, 2010 at 11:39, Brian Quinlan
wrote:
This package eliminates the need to construct the boilerplate
present in
many Python applications i.e. a thread or process pool, a work
queue and
result queue. It also makes it easy
On May 23, 2010, at 8:43 PM, Robert Collins wrote:
On Sun, May 23, 2010 at 10:15 PM, Brian Quinlan
wrote:
Also, you can't fix bugs except by
releasing new versions of Python. Therefore the API must be
completely
stable, and the product virtually bugfree before it should be in
s
On May 23, 2010, at 8:43 PM, Dirkjan Ochtman wrote:
On Sun, May 23, 2010 at 12:15, Brian Quinlan
wrote:
I doubt it. Simple modules are unlikely to develop a following
because it is
too easy to partially replicate their functionality. urlparse and
os.path
are very useful modules but I doubt
On 23 May 2010, at 21:17, Lennart Regebro wrote:
On Sun, May 23, 2010 at 12:15, Brian Quinlan
wrote:
You could make the same argument about any module in the stdlib.
Yeah, and that's exactly what I did.
I doubt it. Simple modules are unlikely to develop a following
because it i
On May 24, 2010, at 5:16 AM, Glyph Lefkowitz wrote:
On May 23, 2010, at 2:37 AM, Brian Quinlan wrote:
On May 23, 2010, at 2:44 PM, Glyph Lefkowitz wrote:
On May 22, 2010, at 8:47 PM, Brian Quinlan wrote:
Jesse, the designated pronouncer for this PEP, has decided to
keep discussion
*right* now"
would be >6 months if it applies in this context.
If that is what "*right* now" means to you then I hope that I never
have a heart attack in your presence and need an ambulance *right*
now :-)
Cheers,
Brian
___
On 26 May 2010, at 18:09, Glyph Lefkowitz wrote:
On May 24, 2010, at 5:36 AM, Brian Quinlan wrote:
On May 24, 2010, at 5:16 AM, Glyph Lefkowitz wrote:
On May 23, 2010, at 2:37 AM, Brian Quinlan wrote:
On May 23, 2010, at 2:44 PM, Glyph Lefkowitz wrote:
ProcessPoolExecutor has the same
Is it possible to have more than one Executor active
at a time?
Of course.
The fact that as_completed() is a module-level
function rather than an Executor method suggests that it
is, but it would be good to have this spelled out one
way or the other in the PEP.
I'll add a note to the global fu
On 26 May 2010, at 22:06, Floris Bruynooghe wrote:
Hi
On Sun, May 23, 2010 at 10:47:08AM +1000, Brian Quinlan wrote:
Jesse, the designated pronouncer for this PEP, has decided to keep
discussion open for a few more days.
So fire away!
In thread.py the module automatically registers a
utures without using an unduly
cumbersome module name, but I don't know how well the PEP explains
that.
It doesn't at all. Are these plans formalized anywhere that I can link
to?
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@p
the queueing strategy to use (e.g. LIFO,
FIFO, priority).
Cheers,
Brian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
g called a ThreadPool.
I think that the "Executor" suffix is a good indicator of the
interface being provided. "Pool" is not because you can could have
Executor implementations that don't involve pools.
Cheers,
Brian
___
On 27 May 2010, at 17:53, Floris Bruynooghe wrote:
On Thu, May 27, 2010 at 01:46:07PM +1200, Greg Ewing wrote:
On 27/05/10 00:31, Brian Quinlan wrote:
You have two semantic choices here:
1. let the interpreter exit with the future still running
2. wait until the future finishes and then
On 28 May 2010, at 09:18, Greg Ewing wrote:
Brian Quinlan wrote:
I think that the "Executor" suffix is a good indicator of the
interface being provided.
It's not usually considered necessary for the name of a
type to indicate its interface. We don't have 'lists
On May 28, 2010, at 11:57 AM, Reid Kleckner wrote:
On Thu, May 27, 2010 at 4:13 AM, Brian Quinlan
wrote:
Keep in mind that this library magic is consistent with the library
magic
that the threading module does - unless the user sets Thread.daemon
to True,
the interpreter does *not* exit
On May 28, 2010, at 1:39 PM, Scott Dial wrote:
On 5/27/2010 4:13 AM, Brian Quinlan wrote:
On 27 May 2010, at 17:53, Floris Bruynooghe wrote:
On Thu, May 27, 2010 at 01:46:07PM +1200, Greg Ewing wrote:
On 27/05/10 00:31, Brian Quinlan wrote:
You have two semantic choices here:
1. let the
On Fri, Jun 18, 2010 at 07:44, anatoly techtonik wrote:
> On Fri, Jun 18, 2010 at 8:07 AM, Stephen Thorne
> wrote:
> >> We are also attempting to enable tax-deductible fund raising to increase
> >> the likelihood of David's finding support. Perhaps we need to think
> >> about a broader campaign t
On Fri, Jul 2, 2010 at 10:16, anatoly techtonik wrote:
> It is not the question about do you like it or not. It is the question
>
>"Are You ready?"
>
> That means:
> Have you tried Mercurial?
>
Yes.
> Do you understand how it works?
Yes.
> Do you have a workflow ready a
(future.result(
- except FutureError:
- print('%r generated an exception: %s' % (url, future.exception()))
+ except FutureError as e:
+ print('%r generated an exception: %s' % (url, e))
Cheers,
Brian
___
Python-Dev maili
On Wed, Jul 14, 2010 at 11:34, Terry Reedy wrote:
> On 7/14/2010 4:10 AM, Georg Brandl wrote:
>
> Sure, and if it was work time, we probably would do this ;). As it is
>> right now, this is volunteer time, and I would say that we're entitled
>> to do whatever helps us getting done the (not alwa
On Thu, Jul 15, 2010 at 13:45, Giampaolo Rodolà wrote:
> Today I was looking for a quick and dirty way to profile a method of a
> class.
> I was thinking that cProfile module had a decorator for this but I was
> wrong so I decided to write one based on hotshot.
> Would it be worth for inclusion?
On Tue, Jul 20, 2010 at 16:53, David Bolen wrote:
> As one of the beneficiaries of the efforts (much appreciated) last
> year to obtain Microsoft MSDN subscriptions for developers/testers (in
> my case, primarily buildbot operation), I was wondering if anyone
> might know if those subscriptions w
On Fri, Jul 23, 2010 at 18:39, Mark Lawrence wrote:
> On 24/07/2010 00:09, Paul Moore wrote:
>
>> On 23 July 2010 23:26, Mark Lawrence wrote:
>>
>>> Is there any money to pay for the forthcoming 10th birthday party for
>>> this
>>> issue? Is the OP still alive?
>>>
>>
>> I'm not sure the sarcasm
which will be replaced with "hg diff".
>
> I proposed using Rietveld like:
> > python -m easy_install review
> > python -m review
>
> But Brian said using Rietveld at all is not a good idea, and didn't
> want to answer what should be done for it to become goo
101 - 200 of 521 matches
Mail list logo
