On 05Jul2013 19:03, Victor Stinner wrote:
| 2013/7/5 Cameron Simpson :
| > | Both set O_NONBLOCK flag (UNIX)
| >
| > Oh, how embarassing.
|
| You said that the PEP is not cristal clear. Do you have a suggestion
| to make it more clear?
|
| Should I mention that the close-on-exec flag is O_CLOEXE
In your first plone example you first use plone.app.content, but then present
the directory structure of plone.app.command.
Apart from that, the PEP seems legit to me, contentwise. I think some parts are
clumsily formulated, but IMO rewriting these parts wouldn't even decrease the
text's length
Hi!
Attached is a an updated proposal for PEP 423.
You can also find it online at https://gist.github.com/benoitbryon/2815051
I am attending at EuroPython 2013 in Florence. Isn't it a great
opportunity to get feedback and discuss about a PEP? I registered an
open-space session and a lightning-
2013/7/5 Cameron Simpson :
> | Both set O_NONBLOCK flag (UNIX)
>
> Oh, how embarassing.
You said that the PEP is not cristal clear. Do you have a suggestion
to make it more clear?
Should I mention that the close-on-exec flag is O_CLOEXEC on UNIX, and
HANDLE_FLAG_INHERIT on Windows? (except that H
ACTIVITY SUMMARY (2013-06-28 - 2013-07-05)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4072 ( +3)
closed 26066 (+39)
total 30138 (+42)
Open issues wit
On 05Jul2013 08:24, Victor Stinner wrote:
| 2013/7/5 Cameron Simpson :
| > You might want to make clear that the "blocking" parameter refers
| > only to the file creation calls (eg socket.socket) and not to the
| > file descriptor itself, and is not to be confused with the UNIX
| > O_NONBLOCK file
Am 04.07.13 18:42, schrieb Chris Withers:
> Hi Guido,
>
> I've bumped into this a couple of times.
>
> First time was when I wanted to know whether what I had was a
> classmethod, staticmethod or normal method here:
>
> https://github.com/Simplistix/testfixtures/blob/master/testfixtures/replace.
2013/7/4 Victor Stinner :
> Even if the PEP 433 was not explicitly rejected, no consensus could be
> reached. I didn't want to loose all my work on this PEP and so I'm
> proposing something new which should make everbody agrees :-)
Thanks Victor, I think this one is perfectly fine!
cf
___
On 5 lip 2013, at 12:07, Martin v. Löwis wrote:
> I wonder why you need to figure out the signatures in advance.
> Can you just wait until the function is actually used, and then
> process the parameters as you get them?
>
My guess is that Michael's design lets mock objects be introspected as w
Am 05.07.13 11:23, schrieb Michael Foord:
> I've also lamented the death of bound methods in Python 3 for mock
> "autospeccing". Autospec introspects objects and provides mock
> objects with the same attributes - and with the same method
> signatures.
I wonder why you need to figure out the signat
On 4 Jul 2013, at 19:00, Guido van Rossum wrote:
> Thanks for the code pointers. So it's all about monkeypatching. :-) I have
> only a little sympathy, as there still seems to be a way to do this, it's
> just less convenient. Too bad.
>
I've also lamented the death of bound methods in Pytho
On 7/4/2013 3:36 PM, Guido van Rossum wrote:
Maybe the mistake is that the others aren't mentioned? Or perhaps
everything before 3.4a1 should be dropped? I forget what kind of policy
we have for this -- is it all changes in this branch or only changes
unique to this branch?
It cannot be 'unique
12 matches
Mail list logo
