Re: [Python-Dev] PEP 554 - strange random boldface

2018-05-13 Thread Steve Holden
On Sat, May 12, 2018 at 4:57 PM, Serhiy Storchaka 
wrote:

> 12.05.18 17:48, Steve Holden пише:
>
>> It's certainly true that when I split any of those left-hand cells the
>> bizarre emphasis occurs. Still looking for a workaround.
>>
>
> Remove an extra indentation of the second line.
>
>
​That's nailed it, thanks!​
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Bugs Migration to OpenShift

2018-05-13 Thread Mark Mangoba
Hi All,

Victor made a good point here.  After discussion with Maciej, we will
postpone this migration to OpenShift until after sprints since bpo
will be heavily used.

Maciej and I will update everyone on the timeline after sprints.

Best regards,
Mark

On Mon, Apr 30, 2018 at 12:54 AM, Victor Stinner  wrote:
> Does it mean that the final switch will happen during the sprints?
> Would it be possible to do it before or after? If bugs.python.org
> doesn't work during the sprint, it will be much harder to contribute
> to CPython during the sprints.
>
> (If I misunderstood, ignore my message :-))
>
> Victor
>
> 2018-04-29 19:07 GMT+02:00 Mark Mangoba :
>> Hi All,
>>
>> We’re planning to finish up the bugs.python.org migration to Red Hat
>> OpenShift by May 14th (US Pycon Sprints).  For the most part
>> everything will stay same, with the exception of cleaning up some old
>> URL’s and redirects from the previous hosting provider:  Upfront
>> Software.
>>
>> We will post a more concrete timeline here by May 1st, but wanted to
>> share this exciting news to move bugs.python.org into a more stable
>> and optimal state.
>>
>> Thank you all for your patience and feedback.  A special thanks to
>> Maciej Szulik and Red Hat for helping the PSF with this project.
>>
>> Best regards,
>> Mark
>>
>> --
>> Mark Mangoba | PSF IT Manager | Python Software Foundation |
>> mmang...@python.org | python.org | Infrastructure Staff:
>> infrastructure-st...@python.org | GPG: 2DE4 D92B 739C 649B EBB8 CCF6
>> DC05 E024 5F4C A0D1
>> ___
>> Python-Dev mailing list
>> Python-Dev@python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe: 
>> https://mail.python.org/mailman/options/python-dev/vstinner%40redhat.com



-- 
Mark Mangoba | PSF IT Manager | Python Software Foundation |
mmang...@python.org | python.org | Infrastructure Staff:
infrastructure-st...@python.org | GPG: 2DE4 D92B 739C 649B EBB8 CCF6
DC05 E024 5F4C A0D1
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] bpo-28055: Fix unaligned accesses in siphash24(). (GH-6123)

2018-05-13 Thread Christian Heimes
On 2018-05-13 06:57, Serhiy Storchaka wrote:
> https://github.com/python/cpython/commit/1e2ec8a996daec65d8d5a3d43b66a9909c6d0653
> commit: 1e2ec8a996daec65d8d5a3d43b66a9909c6d0653
> branch: master
> author: Rolf Eike Beer 
> committer: Serhiy Storchaka 
> date: 2018-05-13T13:57:31+03:00
> summary:
> 
> bpo-28055: Fix unaligned accesses in siphash24(). (GH-6123)
> 
> The hash implementation casts the input pointer to uint64_t* and directly 
> reads
> from this, which may cause unaligned accesses. Use memcpy() instead so this 
> code
> will not crash with SIGBUS on sparc.
> 
> https://bugs.gentoo.org/show_bug.cgi?id=636400
> 
> files:
> A Misc/NEWS.d/next/Core and Builtins/2018-04-25-20-44-42.bpo-28055.f49kfC.rst
> M Python/pyhash.c

Hi Serhiy,

I was against the approach a good reason. The PR adds additional CPU
instructions and changes memory access pattern in a  critical path of
CPython. There is no reason to add additional overhead for the majority
of users or X86 and X86_64 architectures. The memcpy() call should only
be used on architectures that do not support unaligned memory access.
See comment https://bugs.python.org/issue28055#msg276257

At least for latest GCC, the change seems to be fine. GCC emits the same
assembly code for X86_64 before and after your change. Did you check the
output on other CPU architectures as well as clang and MSVC, too?

Christian
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com