On 5/1/2017 1:41 PM, Alexandre Brault wrote:
On 2017-05-01 01:34 PM, Ethan Furman wrote:
On 05/01/2017 07:04 AM, Juancarlo Añez wrote:
On Mon, May 1, 2017 at 9:38 AM, Nick Coghlan wrote:
just support two
keyword arguments to hex(): "delimiter" (as you suggest) and
"chunk_size" (defaulting to
On Thu, Apr 27, 2017 at 7:21 PM, Steven D'Aprano wrote:
> On Wed, Apr 26, 2017 at 03:54:22PM -0400, Jerry Hill wrote:
>> On Tue, Apr 25, 2017 at 8:05 PM, Ryan Gonzalez wrote:
>> > def ___init__(self, self.attr):
>>
>> I'm not a python developer, I'm just a
On 2017-05-01 01:41 PM, Alexandre Brault wrote:
> On 2017-05-01 01:34 PM, Ethan Furman wrote:
>> On 05/01/2017 07:04 AM, Juancarlo Añez wrote:
>>> On Mon, May 1, 2017 at 9:38 AM, Nick Coghlan wrote:
>>>
just support two
keyword arguments to hex(): "delimiter" (as you suggest) and
On 2017-05-01 01:34 PM, Ethan Furman wrote:
> On 05/01/2017 07:04 AM, Juancarlo Añez wrote:
>> On Mon, May 1, 2017 at 9:38 AM, Nick Coghlan wrote:
>>
>>> just support two
>>> keyword arguments to hex(): "delimiter" (as you suggest) and
>>> "chunk_size" (defaulting to 1, so you get per-byte
On 05/01/2017 07:04 AM, Juancarlo Añez wrote:
On Mon, May 1, 2017 at 9:38 AM, Nick Coghlan wrote:
just support two
keyword arguments to hex(): "delimiter" (as you suggest) and
"chunk_size" (defaulting to 1, so you get per-byte chunking by
default)
I'd expect "chunk_size" to mean the number
On Mon, May 1, 2017 at 12:28 AM, Nick Coghlan wrote:
> On 1 May 2017 at 03:07, Guido van Rossum wrote:
> > There's a PR to the peps proposal here:
> > https://github.com/python/peps/pull/242
> >
> > The full text of the current proposal is below. The
On 1 May 2017 at 22:02, Paul Moore wrote:
> On 1 May 2017 at 12:13, NoxDaFox wrote:
>>
>> I think it could be a good fit for the `concurrent.futures` module.
>> Decorated functions would return a `Future` object and run the logic in a
>> separate thread
On 1 May 2017 at 17:19, wrote:
> The bytes.hex() function is the inverse function of Bytes.fromhex().
>
> But fromhex can process spaces (which is much more readable), while hex()
> provides no way to include spaces.
>
> My proposal would be to add an optional delimiter,
On Thu, Apr 27, 2017 at 7:28 PM, Steven D'Aprano
wrote:
> > In my experience, what Python is lacking is a way to declare attributes
> > outside of the constructor. Take a look at how it's done in C#, Swisft,
> or
> > Go.
>
> Since you apparently already know how they do it,
On 1 May 2017 at 12:13, NoxDaFox wrote:
>
> I think it could be a good fit for the `concurrent.futures` module.
> Decorated functions would return a `Future` object and run the logic in a
> separate thread or process.
>
>
> @concurrent.futures.thread
> def function(arg,
The decorators would abstract the logic of spawning a process or thread and
maintaining its lifecycle.
I think it could be a good fit for the `concurrent.futures` module.
Decorated functions would return a `Future` object and run the logic in a
separate thread or process.
On 1 May 2017 at 03:07, Guido van Rossum wrote:
> There's a PR to the peps proposal here:
> https://github.com/python/peps/pull/242
>
> The full text of the current proposal is below. The motivation for this is
> that for complex decorators, even if the type checker can figure
The bytes.hex() function is the inverse function of Bytes.fromhex().
But fromhex can process spaces (which is much more readable), while hex()
provides no way to include spaces.
My proposal would be to add an optional delimiter, that allows to specify a
string that will be inserted between the
13 matches
Mail list logo