On 2018-06-02 07:59:07 +1000, Chris Angelico wrote:
> On Sat, Jun 2, 2018 at 7:03 AM, Peter J. Holzer wrote:
> > On 2018-05-31 14:42:39 -0700, Paul wrote:
> >> I have heard that attachments to messages are not allowed on this list,
> >> which makes sense. However I notice that messages from Peter
On Sat, Jun 2, 2018 at 7:03 AM, Peter J. Holzer wrote:
> On 2018-05-31 14:42:39 -0700, Paul wrote:
>> I have heard that attachments to messages are not allowed on this list,
>> which makes sense. However I notice that messages from Peter do have an
>> attachment, i.e., a signature.asc file.
>
> No
On 2018-05-31 14:42:39 -0700, Paul wrote:
> I have heard that attachments to messages are not allowed on this list,
> which makes sense. However I notice that messages from Peter do have an
> attachment, i.e., a signature.asc file.
No this is isn't an attachment. It's a signature. Your MUA probabl
I gave it a different subject line.
On Fri, Jun 1, 2018 at 2:45 AM, Abdur-Rahmaan Janhangeer <
arj.pyt...@gmail.com> wrote:
> as this sig file is a common occurance, attaching the topic to the data
> blocks thread is not really necessary
>
> Abdur-Rahmaan Janhangeer
> https://github.com/Abdur-rah
as this sig file is a common occurance, attaching the topic to the data
blocks thread is not really necessary
Abdur-Rahmaan Janhangeer
https://github.com/Abdur-rahmaanJ
On Fri, 1 Jun 2018, 01:49 Paul, wrote:
> I have heard that attachments to messages are not allowed on this list,
> which makes
I have heard that attachments to messages are not allowed on this list,
which makes sense. However I notice that messages from Peter do have an
attachment, i.e., a signature.asc file.
I'm just curious; why and how do those particular attachments get through?
And should they get through, I guess? E
On Fri, Jun 1, 2018 at 7:05 AM, Peter J. Holzer wrote:
> [Strange: I didn't get this mail through the list, only directly]
>
> On 2018-05-31 14:39:17 +, Dan Strohl wrote:
>> The outdent method could look like:
>>
>> string.outdent(size=None)
>> """
>> :param size : The number of spaces
On 2018-05-31 23:05:35 +0200, Peter J. Holzer wrote:
> [Strange: I didn't get this mail through the list, only directly]
Found it. For some reason "Avoid duplicate copies of messages" was
enabled. I normally always disable this when I subscribe to a
mailinglist and I'm surprised that I haven't not
[Strange: I didn't get this mail through the list, only directly]
On 2018-05-31 14:39:17 +, Dan Strohl wrote:
> > This is of course not a problem if the *trailing* quote determines the
> > indentation:
> >
> > a_multi_line_string = i'''
> >Py-
> > thon
> > ''
On Fri, Jun 1, 2018 at 12:39 AM, Dan Strohl via Python-list
wrote:
>> This is of course not a problem if the *trailing* quote determines the
>> indentation:
>>
>> a_multi_line_string = i'''
>>Py-
>> thon
>> '''
>
> I get the point, but it feels like it would be a
> This is of course not a problem if the *trailing* quote determines the
> indentation:
>
> a_multi_line_string = i'''
>Py-
> thon
> '''
I get the point, but it feels like it would be a pain to use, and it "Feels"
different from the other python indenting, which
On 2018-05-29 07:57:18 -0600, Ian Kelly wrote:
> On Tue, May 29, 2018 at 3:19 AM, Peter J. Holzer wrote:
> > On 2018-05-23 11:08:48 -0600, Ian Kelly wrote:
> >>
[...]
> > What if I want all lines to start with some white space?
[...]
>
> Fair points.
[...]
> >> Also, how about using a string pr
On Tue, May 29, 2018 at 3:19 AM, Peter J. Holzer wrote:
> On 2018-05-23 11:08:48 -0600, Ian Kelly wrote:
>>
>> How about we instead just use the rules from PEP 257 so that there
>> aren't two different sets of multi-line string indentation rules to
>> have to remember?
>>
>> https://www.python.org
On 2018-05-23 11:08:48 -0600, Ian Kelly wrote:
> On Wed, May 23, 2018 at 10:25 AM, Peter J. Holzer wrote:
> > How about this?
> >
> > x =
> > Here is a multi-line string
> > with
> > indentation.
> >
> >
> > This would be equivalent to
> >
> >
On Thu, May 24, 2018 at 3:08 AM, Ian Kelly wrote:
> I don't know if 'i' would be the right prefix character for this, but
> it's unused and is short for 'indented':
>
> b = i'''
> Here is a multi-line string
> with indentation, which is
> determined from the second
> line.'''
Sinc
>
> How about we instead just use the rules from PEP 257 so that there aren't two
> different sets of multi-line string indentation rules to have to remember?
>
> https://www.python.org/dev/peps/pep-0257/#handling-docstring-indentation
>
I like that, better to be closer to the existing stand
On Wed, May 23, 2018 at 10:25 AM, Peter J. Holzer wrote:
> How about this?
>
> x =
> Here is a multi-line string
> with
> indentation.
>
>
> This would be equivalent to
>
> x = 'Here is a multi-line string\nwith\n indentation.'
>
> Rules
>
> > Personally though, I would not hard code it to knock out 4 leading
> > spaces. I would have it handle spaces the same was that the existing
> > parser does, if there are 4 spaces indending the next line, then it
> > removes 4 spaces, if there are 6 spaces, it removes 6 spaces, etc...
> >
18 matches
Mail list logo
