On 6/16/2012 6:40 PM, Yury Selivanov wrote:
Actually, Signature and Parameter are currently non-hashable (they are
mutable). I'm not sure if it was a right decision.
If this is added for 3.3, I think it would be a candidate for
'provisional' (ie, api subject to change) status. (That is not t
On Thu, Jun 14, 2012 at 1:57 PM, "Martin v. Löwis" wrote:
> > I don't really see the point. In my experience there is no benefit to
> > removing assert statements in production mode. This is a C-specific
> > notion that doesn't really map very well to Python code. Do other
> > high-level languages
I have an idle x86 Solaris 11 workstation (with SolarisStudio12.3)
that is ready to be a build slave, it just needs credentials to
participate.
Thank you,
--
Justin Venus
justin.ve...@gmail.com
___
Python-Dev mailing list
Python-Dev@python.org
http://m
On 2012-06-16, at 11:27 AM, Nick Coghlan wrote:
> On Sat, Jun 16, 2012 at 1:56 PM, Jim J. Jewett wrote:
>>
>> Summary:
>>
>>*Every* Parameter attribute is optional, even name. (Think of
>>builtins, even if they aren't automatically supported yet.)
>>So go ahead and define some othe
Jim,
On 2012-06-15, at 11:56 PM, Jim J. Jewett wrote:
> because:
>def f(*, a=4, b=5): pass
>
> and:
>def f(*, b=5, a=4): pass
>
> should probably have equal signatures.
That's a very good catch -- I'll fix the implementation.
>> * bind(\*args, \*\*kwargs) -> BoundArguments
>>Create
On Sat, Jun 16, 2012 at 1:56 PM, Jim J. Jewett wrote:
>
> Summary:
>
> *Every* Parameter attribute is optional, even name. (Think of
> builtins, even if they aren't automatically supported yet.)
> So go ahead and define some others that are sometimes useful.
No, that's not the right att
On Sat, Jun 16, 2012 at 10:52 AM, Benjamin Peterson wrote:
> 2012/6/15 Larry Hastings :
>> Note that I'm genuinely interested in your answer--"is_implemented" appears
>> to have a groundswell of anti-support and I rather suspect will be axed.
>> Meantime I still need to solve this problem.
>
> How
On Fri, Jun 15, 2012 at 11:24 PM, Larry Hastings wrote:
> There are four more candidates I found with the grep but couldn't figure out
> how to instantiate and test. They have to do with the descriptor protocol,
> aka properties, but the types aren't directly exposed by Python. They're
> all def
On Sat, Jun 16, 2012 at 5:56 AM, Jim J. Jewett wrote:
> I think it should be explicit that this mapping does not include
> parameters which would be filled by default arguments. In fact, if
> you stick with this interface, I would like a 3rd method that does
> fill out everything.
+1
Daniel
__
On Sat, 16 Jun 2012 02:29:09 +0200
victor.stinner wrote:
> +if (from_kind == to_kind) {
> +if (!PyUnicode_IS_ASCII(from) && PyUnicode_IS_ASCII(to)) {
> +/* Writing Latin-1 characters into an ASCII string requires to
> + check that all written characters are pu
10 matches
Mail list logo
