On 10/12/2013 11:57 PM, Nick Coghlan wrote:
For the record, this thread did prompt me to consider the new
construct anew, but on reflection, I still consider it a reasonable
addition to contextlib.
It substantially improves the simple cases it is intended to help
with, and, if anything, mak
On 14 Oct 2013 04:26, "Paul Moore" wrote:
>
> On 13 October 2013 13:43, Nick Coghlan wrote:
> > Accordingly, in addition to adding the option to extract and install
``pip``
> > during installation, this PEP proposes that the Windows installer (and
> > ``sysconfig``) in Python 3.4 and later be upd
On 14 Oct 2013 01:45, "Antoine Pitrou" wrote:
>
> On Mon, 14 Oct 2013 01:20:30 +1000
> Nick Coghlan wrote:
> >
> > Then, yes, I think challenging people to try to get me booted as
> > module maintainer for contextlib is a *precisely* proportionate
> > response.
>
> Because I don't agree with you
On Sun, Oct 13, 2013 at 1:58 PM, Alexander Belopolsky
wrote:
> People who write code using contextlib
> are expected to know
People who *read* that code while learning Python cannot be expected
to know that it is not really possible to ignore errors in Python.
If this feature is used under any n
Le 13 oct. 2013 10:19, "Stefan Behnel" a écrit :
> I agree. I find it much easier to read a plain and obvious
>
> try:
>from _cmodule import *
> except ImportError:
>from _pymodule import *
>
> in a facade module ...
I miss maybe something. I don't understand why you would
On 13 October 2013 13:43, Nick Coghlan wrote:
> Accordingly, in addition to adding the option to extract and install ``pip``
> during installation, this PEP proposes that the Windows installer (and
> ``sysconfig``) in Python 3.4 and later be updated to:
>
> - install scripts to PythonXY\bin rather
On Sun, Oct 13, 2013 at 2:09 PM, R. David Murray wrote:
> with replaces try/finally, not try/except.
with ignore(..) is different. This is one of the things that I like
about it - a demonstration of a context manager that replaces
try/except.
___
Pytho
Oscar Benjamin, 13.10.2013 18:35:
> CPython preferentially imports extension modules over .py modules with
> the same name. This is what happens when you use Cython in "pure"
> mode: You have a pure mod.py file and an "augmenting" mod.pxd that
> contains the annotations relevant to Cython. The resu
On Sun, 13 Oct 2013 13:58:56 -0400, Alexander Belopolsky
wrote:
> The feature (*and* its name) is a fine solution for the problem that
> it solves and is an improvement over status quo.
>
> I find
>
> with ignore(OSError):
> os.unlink(path)
>
> much easier to read than
>
> try:
>os.u
On Sun, Oct 13, 2013 at 1:01 PM, R. David Murray wrote:
> But the name hurts my brain
I did not think I would weigh in on this because Ramond's and Nick's
position seemed quite rational and the issue minor, but surprisingly
this thread does not seem to end.
The feature (*and* its name) is a fine
The feedback on the previous version of PEP 453 could be summed up as
"yes for 3.4, no for 2.7 and 3.3", and I've now updated the PEP
accordingly.
HTML: http://www.python.org/dev/peps/pep-0453/
Main diff: http://hg.python.org/peps/rev/405b80d54b7d (there are
additional minor cleanup diffs after th
+1 to the below.
I don't have a strong opinion about the feature itself. The number of
times I can imagine using it in code is pretty close to zero, but
might not actually turn out to *be* zero, you never know.
But the name hurts my brain for the reasons PJ explains :)
--David
PS: I think you
On 12 October 2013 17:55, Christian Heimes wrote:
> Am 12.10.2013 17:37, schrieb Nick Coghlan:
>> I think the default recommendation in PEP 399 still makes sense - 2
>> modules are easy to manage than three and the idiom allows for easy
>> partial replacement.
>
> We could ues yet another approach
On Sun, Oct 13, 2013 at 10:05 AM, Antoine Pitrou wrote:
> And for the record, it's not *my* objection; several other core
> developers have said -1 too: Ezio, Serhiy, Giampaolo, etc.
FWIW, I'm -1 also; the thread quickly convinced me that this is a
horrible idea, at least with the current name.
On Mon, 14 Oct 2013 01:20:30 +1000
Nick Coghlan wrote:
>
> Then, yes, I think challenging people to try to get me booted as
> module maintainer for contextlib is a *precisely* proportionate
> response.
Because I don't agree with you on one instance doesn't mean I usually
*distrust* your judgemen
On 14 October 2013 00:05, Antoine Pitrou wrote:
> On Sun, 13 Oct 2013 22:50:07 +1000
> Nick Coghlan wrote:
>> That's the way this works (unless you think this is such a disastrous
>> addition that you want to appeal to Guido to strip me of my
>> responsibilities as contextlib maintainer and go hu
On 14 October 2013 01:05, Victor Stinner wrote:
> 2013/10/13 Ethan Furman :
>> True, but Raymond's example of
>>
>> with ignore(OSError):
>> os.remove('somefile')
>
> And what about:
>
> with ignore(OSError):
> os.remove('file1')
> os.remove('file2')
It's just as broken as the try
2013/10/13 Ethan Furman :
> True, but Raymond's example of
>
> with ignore(OSError):
> os.remove('somefile')
And what about:
with ignore(OSError):
os.remove('file1')
os.remove('file2')
?
Victor
___
Python-Dev mailing list
Python-Dev@py
On 10/13/2013 05:34 AM, Antoine Pitrou wrote:
On Sun, 13 Oct 2013 16:57:09 +1000
Nick Coghlan wrote:
For the record, this thread did prompt me to consider the new construct
anew, but on reflection, I still consider it a reasonable addition to
contextlib.
It substantially improves the simple c
On 10/13/2013 04:44 AM, Nick Coghlan wrote:
On 13 Oct 2013 08:27, "Ethan Furman" wrote:
It was pointed in Issue16938[1] that __objclass__ is not documented anywhere.
Is the following an appropriate description? (in Doc/reference/datamodel.rst in
user-defined functions)
+---
2013/10/13 Antoine Pitrou :
> On Sun, 13 Oct 2013 22:50:07 +1000
> Nick Coghlan wrote:
>> That's the way this works (unless you think this is such a disastrous
>> addition that you want to appeal to Guido to strip me of my
>> responsibilities as contextlib maintainer and go hunting for a new
>> on
13.10.13 15:50, Nick Coghlan написав(ла):
On 13 October 2013 22:34, Antoine Pitrou wrote:
There's actually more typing involved, and one more API to know about...
It is just another case of those "one-liners" that we generally refrain
from adding to the stdlib.
It meets my threshold for inclu
On Sun, 13 Oct 2013 16:05:40 +0200
Antoine Pitrou wrote:
> On Sun, 13 Oct 2013 22:50:07 +1000
> Nick Coghlan wrote:
> > That's the way this works (unless you think this is such a disastrous
> > addition that you want to appeal to Guido to strip me of my
> > responsibilities as contextlib maintain
On Sun, 13 Oct 2013 22:50:07 +1000
Nick Coghlan wrote:
> That's the way this works (unless you think this is such a disastrous
> addition that you want to appeal to Guido to strip me of my
> responsibilities as contextlib maintainer and go hunting for a new
> one).
Wow... I don't think challengin
On 13 October 2013 22:34, Antoine Pitrou wrote:
> On Sun, 13 Oct 2013 16:57:09 +1000
> Nick Coghlan wrote:
>>
>> For the record, this thread did prompt me to consider the new construct
>> anew, but on reflection, I still consider it a reasonable addition to
>> contextlib.
>>
>> It substantially i
On Sun, 13 Oct 2013 16:57:09 +1000
Nick Coghlan wrote:
>
> For the record, this thread did prompt me to consider the new construct
> anew, but on reflection, I still consider it a reasonable addition to
> contextlib.
>
> It substantially improves the simple cases it is intended to help with,
> a
On 13 October 2013 20:39, Christian Heimes wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am 13.10.2013 08:32, schrieb Nick Coghlan:
>> +1 to hashlib from me (especially since we used that as the best
>> available home for compare_digest).
>
> I'm afraid your memory doesn't serve y
Stefan Behnel wrote:
> in a facade module than
>
> # lots and lots
> # of unused
> # Python code
> # here ...
>
> # ... and then this, well hidden at the end, telling
> # me that I just waded through the entirely wrong code:
>
> try:
>from _cmodule import *
>
On 13 Oct 2013 08:27, "Ethan Furman" wrote:
>
> It was pointed in Issue16938[1] that __objclass__ is not documented anywhere.
>
> Is the following an appropriate description? (in Doc/reference/datamodel.rst
> in user-defined functions)
>
>
>
> +-+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 13.10.2013 08:32, schrieb Nick Coghlan:
> +1 to hashlib from me (especially since we used that as the best
> available home for compare_digest).
I'm afraid your memory doesn't serve you well. :(
compare_digest is implemented in _operator.c. Its
Antoine Pitrou, 12.10.2013 23:40:
> On Sat, 12 Oct 2013 23:35:23 +0200
> Christian Heimes wrote:
>> A directory with pure Python modules is less cumbersome than a couple
>> of facade modules or intended code in try/except ImportError blocks.
>
> I don't find it cumbersome to be explicit here. It m
On 10/12/2013 11:18 PM, Cameron Simpson wrote:
On 12Oct2013 15:03, Ethan Furman wrote:
It was pointed in Issue16938[1] that __objclass__ is not documented anywhere.
Is the following an appropriate description? (in Doc/reference/datamodel.rst in
user-defined functions)
+
32 matches
Mail list logo
