Adding support to Unicode characters over codepoint 0xffff#63
Adding support to Unicode characters over codepoint 0xffff#63sigmavirus24 merged 5 commits intoyaml:masterfrom
Conversation
|
|
||
| PyYAML is written by Kirill Simonov <xi@resolvent.net>. It is released | ||
| under the MIT license. See the file LICENSE for more details. | ||
|
|
There was a problem hiding this comment.
removing trailing newlines is bad form as it's diff noise. I'd undo it for all the files you've added it for, which seems to be every file you've touched. Also files should end with a trailing newline to be POSIX valid
| if index == 0: | ||
| # Leading indicators are special characters. | ||
| if ch in u'#,[]{}&*!|>\'\"%@`': | ||
| if ch in u'#,[]{}&*!|>\'\"%@`': |
There was a problem hiding this comment.
trimming trailing whitespace is bad form as it's diff noise
|
Adam,
Please feel free to do the changes as you see fit. I don't know why they
happened at all. Perhaps the editor I was using (Atom on Linux Mint x64) is
to blame.
Best regards,
Peter
…On Wed, May 10, 2017 at 7:21 PM, Adam Johnson ***@***.***> wrote:
***@***.**** requested changes on this pull request.
------------------------------
In README <#63 (comment)>:
> @@ -32,4 +32,3 @@ Submit bug reports and feature requests to the PyYAML bug tracker:
PyYAML is written by Kirill Simonov ***@***.***>. It is released
under the MIT license. See the file LICENSE for more details.
-
removing trailing newlines is bad form as it's diff noise. I'd undo it for
all the files you've added it for, which seems to be every file you've
touched. Also files should end with a trailing newline to be POSIX valid
------------------------------
In lib/yaml/emitter.py
<#63 (comment)>:
> @@ -674,7 +678,7 @@ def analyze_scalar(self, scalar):
# Check for indicators.
if index == 0:
# Leading indicators are special characters.
- if ch in u'#,[]{}&*!|>\'\"%@`':
+ if ch in u'#,[]{}&*!|>\'\"%@`':
trimming trailing whitespace is bad form as it's diff noise
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#63 (review)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA-AtYWG4MJjDFP9prMvmTILeunl8Nkiks5r4YGDgaJpZM4NWBnY>
.
--
Email: peterkmurphy@gmail.com
WWW: http://www.pkmurphy.com.au/
|
|
@peterkmurphy I'm not an admin on this project, I can't do anything to your PR. |
|
you may need to ping @sigmavirus24 or another commiter for this project to get this merged and a new release made. |
|
I copied this and tidied it up in #65 |
|
Adam,
That's probably for the best. I will keep my pull request up until yours is
integrated into the main branch; it contains some explanatory notes. After
that, I'll withdraw mine.
Thanks for cleaning up.
Best regards,
Peter
…On Tue, May 16, 2017 at 7:38 PM, Adam Johnson ***@***.***> wrote:
I copied this and tidied it up in #65
<#65>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA-Ates03dkvncNnSz2JgYVMklsghcJTks5r6W6jgaJpZM4NWBnY>
.
--
Email: peterkmurphy@gmail.com
WWW: http://www.pkmurphy.com.au/
|
|
Thanks @peterkmurphy! 🎉 ✨ |
|
@ingydotnet is there any chance this fix could be backported to the cc @nitzmahone |
|
I'd be +1 for that |
|
@perlpunk and I are meeting up in a week. We might be able to discuss it then. |
This patch is aimed at solving issue #25 . As a side effect, the testing code has been trimmed to accommodate the fixes. Why have I done that? I might as well repeat what I said on gmail:
In some cases I have altered testing code; others I have removed them.