[issue26249] Change PyMem_Malloc to use PyObject_Malloc allocator?

[Alecsandru Patrascu]

Changes by Alecsandru Patrascu :


--
nosy: +alecsandru.patrascu

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25924] investigate if getaddrinfo(3) on OSX is thread-safe

[Ned Deily]

Ned Deily added the comment:

I've committed a revised version of the "try 2" patch for release in 2.7.12, 
3.5.2, and 3.6.0.  The revisions were to better follow the somewhat arcane 
conventions of Apple's availability macros, in particular, to take into account 
the value of MACOSX_DEPLOYMENT_TARGET.  I didn't have an opportunity to test 
building it on an actual 10.4 (or 10.3 :) system but I did test with various 
settings of MACOSX_DEPLOYMENT_TARGET.  Thanks very much, Jesse, for the 
research and the patch and to everyone else for the reviews and comments.

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[Mathieu Dupuy]

Mathieu Dupuy added the comment:

slightly improved + addresses issues stated here : 
https://bugs.python.org/review/15873/diff/16581/Lib/datetime.py#newcode1418Lib/datetime.py:1418

--
Added file: http://bugs.python.org/file41926/fromisoformat3.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25924] investigate if getaddrinfo(3) on OSX is thread-safe

[Roundup Robot]

Roundup Robot added the comment:

New changeset 58ebfa7c1361 by Ned Deily in branch '2.7':
Issue #25924: Avoid unnecessary serialization of getaddrinfo(3) calls on OS X
https://hg.python.org/cpython/rev/58ebfa7c1361

New changeset 86ddb4d747f8 by Ned Deily in branch '3.5':
Issue #25924: Avoid unnecessary serialization of getaddrinfo(3) calls on OS X
https://hg.python.org/cpython/rev/86ddb4d747f8

New changeset caca2b354773 by Ned Deily in branch 'default':
Issue #25924: merge with 3.5
https://hg.python.org/cpython/rev/caca2b354773

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26268] Update python.org installers to use OpenSSL 1.0.2f

[Roundup Robot]

Roundup Robot added the comment:

New changeset 1ceb431e1876 by Ned Deily in branch '2.7':
Issue #26268: Update OS X 10.5+ installer build to use OpenSSL 1.0.2f.
https://hg.python.org/cpython/rev/1ceb431e1876

New changeset 3c3eae72dd04 by Ned Deily in branch '3.5':
Issue #26268: Update OS X 10.5+ installer build to use OpenSSL 1.0.2f.
https://hg.python.org/cpython/rev/3c3eae72dd04

New changeset 6759581f9fd3 by Ned Deily in branch 'default':
Issue #26268: merge from 3.5
https://hg.python.org/cpython/rev/6759581f9fd3

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26362] Approved API for creating a temporary file path

[Ethan Furman]

Changes by Ethan Furman :


--
nosy: +ethan.furman

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[Mathieu Dupuy]

Mathieu Dupuy added the comment:

discarding the microseconds digits after the 6th.

2016-02-15 13:30 GMT+10:30 karl :

>
> karl added the comment:
>
> About
>
> > Actually, I realized that the best implementation of parsing rfc 3339
> > is in django dateparse utils. To me it's the finest, the most
> > elegant, and no other one can claim to be more robust since it's
> > probably the #1 iso parsing functions used in python. Have a look at
> >
> https://docs.djangoproject.com/en/1.9/_modules/django/utils/dateparse/#parse_datetime
>
> How does it parse this date:
>
> 2016-02-15T11:59:46.16588638674+09:00
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[karl]

karl added the comment:

About

> Actually, I realized that the best implementation of parsing rfc 3339 
> is in django dateparse utils. To me it's the finest, the most 
> elegant, and no other one can claim to be more robust since it's 
> probably the #1 iso parsing functions used in python. Have a look at 
> https://docs.djangoproject.com/en/1.9/_modules/django/utils/dateparse/#parse_datetime

How does it parse this date: 

2016-02-15T11:59:46.16588638674+09:00

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[karl]

karl added the comment:

>From https://www.djangoproject.com/foundation/cla/faq/

> Am I giving away the copyright to my contributions?
> 
> No. This is a pure license agreement, not a copyright assignment. You 
> still maintain the full copyright for your contributions. You are 
> only providing a license to the DSF to distribute your code without 
> further restrictions. This is not the case for all CLA's, but it is 
> the case for the one we are using.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[Mathieu Dupuy]

Mathieu Dupuy added the comment:

I don't know. The taken code is really little, modified, and is nothing much 
that an implementation you had seen a while ago, and recoded by memory not 
remembering where you saw it in the first place. Do you think that's really an 
issue ?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26362] Approved API for creating a temporary file path

[Ben Finney]

New submission from Ben Finney:

The security issues of `tempfile.mktemp` are clear when the return value is 
used to create a filesystem entry. The documentation and docstrings (and even 
some comments on past issues) are correct o deprecate its use for that purpose.

The function has a use which doers not have security implications: generating 
test data. When a test case wants to generate unpredictable, unique, valid 
filesystem paths – and *never access those paths* on the filesystem – the 
`tempfile.mktemp` function is right there and is very useful.

The `tempfile._RandomNameSequence` class would also be useful, but its name 
also makes clear that it is not part of the library public API.

Please make that functionality available for the purpose of *only* generating 
filesystem paths as `tempfile._RandomNameSequence` does, in a public, 
supported, non-deprecated API.

--
components: Library (Lib)
messages: 260291
nosy: bignose
priority: normal
severity: normal
status: open
title: Approved API for creating a temporary file path
type: behavior
versions: Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26361] lambda in dict comprehension is broken

[Eryk Sun]

Eryk Sun added the comment:

For Python 3 you can also make it a keyword-only argument by adding a bare '*' 
to the parameter list:

funcs = [(lambda x, *, t=t: x * t) for t in range(5)]

Code that accidentally calls funcs[0](3, 'silent bug ') will raise a TypeError 
because "t" can only be passed as a keyword argument.

An alternative is to use another lambda instead of using a default argument:

funcs = [(lambda y: (lambda x:  x * y))(t) for t in range(5)]

This lets you continue to use a closure (now over the temporary scope of the 
outer call) and keep the function signature free of extra arguments. However, 
using a keyword-only argument is obviously less obfuscated.

--
nosy: +eryksun

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26361] lambda in dict comprehension is broken

[Steven D'Aprano]

Steven D'Aprano added the comment:

This is the standard behaviour of closures in Python. It's annoying, and often 
not what you expect, but it's not a bug.

Effectively, your dict or list contains five functions, each of which refer to 
the same variable "t". By the time the loop finishes, that variable has the 
value 4, so naturally all five functions see the same value for t.

The standard work-around is to use the default-argument trick to take a 
snapshot of the current value of the variable at the moment the function is 
created:

[(lambda x, t=t: x * t) for t in range(5)]

--
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26361] lambda in dict comprehension is broken

[Samuel Ainsworth]

Samuel Ainsworth added the comment:

Also applies to list comprehensions. For example, 

lst = [(lambda x: x * t) for t in range(5)]
lst[0](1)   # => 4

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19841] ConfigParser PEP issues

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the patch, Ivailo.

The following changes are going to break the public API:

-def get(self, section, option, raw=False, vars=None):
+def get(self, section, option, raw=False, vvars=None):

-def items(self, section, raw=False, vars=None):
+def items(self, section, raw=False, vvars=None):

Also,

-class RawConfigParser:
+class RawConfigParser(object):

There are a few differences between old-style and new-style classes. 
RawConfigParser implements collections.abs.MutableMapping so this isn't a 
problem in Python 3.

Closing this as "won't fix".

--
nosy: +berker.peksag
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26361] lambda in dict comprehension is broken

[Samuel Ainsworth]

New submission from Samuel Ainsworth:

If we construct a dict as follows,

x = {t: lambda x: x * t for t in range(5)}

then `x[0](1)` evaluates to 4! Tested on 2.7 and 3.5.

--
messages: 260287
nosy: Samuel.Ainsworth
priority: normal
severity: normal
status: open
title: lambda in dict comprehension is broken
type: behavior
versions: Python 2.7, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26215] Make GC_Head a compile-time option

[yuriy_levchenko]

yuriy_levchenko added the comment:

I'm going to do this under define, as an option. In my application it consumes 
several mBs + it's some performance for handling  this structure.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12806] argparse: Hybrid help text formatter

[Mark Lawrence]

Changes by Mark Lawrence :


--
nosy:  -BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Mark Dickinson]

Mark Dickinson added the comment:

Update: I *have* been able to reproduce in a debug build. Here's the stack 
trace.

--
Added file: http://bugs.python.org/file41924/debug-build-stacktrace.txt

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Mark Dickinson]

Mark Dickinson added the comment:

One thing that looks a bit odd to my eyes is the different values for `lock` in 
the PyThread_acquire_lock calls (see below). All of threads 2-5 should be 
waiting on the GIL, so I'd expect to see the same value for `lock` in all those 
calls. Instead, threads 2 and 5 seem to be waiting on the same lock, but 
threads 3 and 4 seem to have their own lock. But I don't know this code well 
enough to know whether it's supposed to be this way.

Thread 5 (Thread 0x1903 of process 14075):
#2  0x0001000e7e21 in PyThread_acquire_lock (lock=0xed3ed500, 
waitflag=) at Python/thread_pthread.h:429

Thread 4 (Thread 0x1803 of process 14075):
#2  0x0001000e7e21 in PyThread_acquire_lock (lock=0xed3ed300, 
waitflag=) at Python/thread_pthread.h:429

Thread 3 (Thread 0x1703 of process 14075):
#2  0x0001000e7e21 in PyThread_acquire_lock (lock=0xed3ed600, 
waitflag=) at Python/thread_pthread.h:429

Thread 2 (Thread 0x1603 of process 14075):
#2  0x0001000e7e21 in PyThread_acquire_lock (lock=0xed3ed300, 
waitflag=) at Python/thread_pthread.h:429

Thread 1 (Thread 0x1503 of process 14075):
#2  0x0001000e7e21 in PyThread_acquire_lock (lock=0x0, waitflag=) at Python/thread_pthread.h:429

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Mark Dickinson]

Mark Dickinson added the comment:

> threads 2 and 5

Sorry, that should have said "threads 2 and 4".

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Mark Dickinson]

Mark Dickinson added the comment:

> lock=0x0 looks suspicious.

Agreed. I think that *could* possibly be a consequence of the earlier multiple 
GILs, though I haven't figured out exactly how yet.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[STINNER Victor]

STINNER Victor added the comment:

Is the django license compatible with the Python license?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

lock=0x0 looks suspicious.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[Mathieu Dupuy]

Mathieu Dupuy added the comment:

(slightly improved version, better use of timedelta)

--
Added file: http://bugs.python.org/file41923/fromisoformat2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8706] accept keyword arguments on most base type methods and builtins

[Nicholas Chammas]

Changes by Nicholas Chammas :


--
nosy: +Nicholas Chammas

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25351] pyvenv activate script failure with specific bash option

[Vinay Sajip]

Vinay Sajip added the comment:

Can you try the attached script in place of the current activate script and see 
if it meets the requirements?

--
Added file: http://bugs.python.org/file41925/activate

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[Mathieu Dupuy]

Mathieu Dupuy added the comment:

Here is the PoC with code taken from django.utils.parse_datetime and adapted 
for the datetime module (I didn't ask for their agreement yet). Of course tests 
pass. For me it's the most elegant solution.

(I think date and time also need their "fromisotimestamp" counterpart).

--
Added file: http://bugs.python.org/file41922/fromisoformat.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24915] Profile Guided Optimization improvements (better training, llvm support, etc)

[Alecsandru Patrascu]

Changes by Alecsandru Patrascu :


--
resolution: fixed -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26307] no PGO for built-in modules with `make profile-opt`

[Alecsandru Patrascu]

Alecsandru Patrascu added the comment:

I've added a fix for the PGO builds after the issue pointed out by you. Can you 
please test it also?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Mark Dickinson]

Mark Dickinson added the comment:

Here's the hanging code as an attached file.

--
Added file: http://bugs.python.org/file41921/threading_hang.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Mark Dickinson]

New submission from Mark Dickinson:

On OS X (10.9.5), I'm getting an apparent deadlock in the following simple 
Python script:

#
import itertools
import threading

def is_prime(n):
return n >= 2 and all(n % d for d in xrange(2, n))

def count_primes_in_range(start, stop):
return sum(is_prime(n) for n in xrange(start, stop))

def main():
threads = [
threading.Thread(
target=count_primes_in_range,
args=(12500*i, 12500*(i+1))
)
for i in xrange(8)
]
for thread in threads:
thread.start()
for thread in threads:
thread.join()


if __name__ == '__main__':
for i in itertools.count():
print "Iteration: ", i
main()
#

Each iteration takes around 60 seconds, and I typically get a deadlock within 
the first 5 iterations. It looks as though the deadlock happens during the 
"thread.join", at a stage where some of the threads have already completed and 
been joined. The code hangs with no CPU activity, and a backtrace (attached) 
shows that all the background threads are waiting for the GIL, while the main 
thread is in a blocking `thread.join` call.

I've attached a gdb-generated stack trace.

I was unable to reproduce this with a debug build of Python. I *have* 
reproduced with a normal build of Python, and on various Python 2.7 executables 
from 3rd party sources (Apple, Macports, Enthought Canopy).

I've also not yet managed to reproduce on Python 3, but I haven't tried that 
hard. I suspect it's a Python 2-only problem, though.

(And yes, this is horrible code that doesn't make much sense. It's actually a 
cut-down example from a "how not to do it" part of a course on concurrency. 
Nevertheless, it shouldn't be deadlocking.)

--
components: Interpreter Core
files: hang_backtrace.txt
messages: 260273
nosy: mark.dickinson
priority: normal
severity: normal
status: open
title: Deadlock in thread.join
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file41920/hang_backtrace.txt

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15873] datetime: add ability to parse RFC 3339 dates and times

[Mathieu Dupuy]

Mathieu Dupuy added the comment:

#12006 will unfortunately of no use for this one.

Actually, I realized that the best implementation of parsing rfc 3339 is in 
django dateparse utils. To me it's the finest, the most elegant, and no other 
one can claim to be more robust since it's probably the #1 iso parsing 
functions used in python. Have a look at 
https://docs.djangoproject.com/en/1.9/_modules/django/utils/dateparse/#parse_datetime

Alexander, I won't start before I have your opinion. What do you think ?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24165] Free list for single-digits ints

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

> 99% of all long allocations are coming from freelist when it's there.

Detailed statistics from a test suite run see in msg242886. Only a half of ints 
are single-digit with 15-bit digits, and 3/4 with 30-bit digits. 86% of ints 
are 32-bit. The majority of ints (about 2/3) are small ints in the range 
[-5..256]. These patches don't affect them.

That is why the effect of patches is not very significant.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24165] Free list for single-digits ints

[Antoine Pitrou]

Antoine Pitrou added the comment:

The test suite can't really be representative of common workloads and it isn't 
meant to be.

The real question is not so much if the freelist helps reduce the number of 
integer allocations (it's obvious it will), it's whether doing so actually 
speeds up Python significantly. The small object allocator is quite fast.

If freelisting one-digit integers doesn't bring any tangible benefits, it's 
unlikely that freelisting two-digit integers will. The general distribution of 
integers probably follows some kind of power law (which is why small integers 
are interned).

And since most installs are probably 64-bit nowadays, single-digit integers go 
up to 2**30, which covers the immense majority of uses.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26359] CPython build options for out-of-the box performance

[Alecsandru Patrascu]

New submission from Alecsandru Patrascu:

Hello,

This is Alecsandru from the Dynamic Scripting Languages Optimization Team at 
Intel Corporation. I would like to submit a patch as a response to the 
discussion thread opened in Python-Dev 
(https://mail.python.org/pipermail/python-dev/2016-February/143215.html), 
regarding the way CPython is built, mainly the options that are available to 
the programmers. Analyzing the CPython ecosystem we can see that there are a 
lot of users that just download the sources and hit the commands "./configure", 
"make" and "make install" once and then continue using it with their Python 
scripts. One of the problems with this workflow it that the users do not 
benefit from the entire optimization features that are existing in the build 
system, such as PGO and LTO.

Therefore, I propose a workflow, like the following. Assume some work has to be 
done into the CPython interpreter, a developer can do the following steps:
A. Implementation and debugging phase. 
1. The command "./configure PYDIST=debug" is ran once. It will enable the 
Py_DEBUG, -O0 and -g flags
2. The command "make" is ran once or multiple times

B. Testing the implementation from step A, in a pre-release environment
1. The command "./configure PYDIST=devel" is ran once. It will disable the 
Py_DEBUG flags and will enable the -O3 and -g flags, and it is just like the 
current implementation in CPython
2. The command "make" is ran once or multiple times

C. For any other CPython usage, for example distributing the interpreter, 
installing it inside an operating system, or just the majority of users who are 
not CPython developers and only want to compile it once and use it as-is:
1. The command "./configure" is ran once. Alternatively, the command  
"./configure PYDIST=release" can be used. It will disable all debugging 
functionality, enable the -O3 flag and will enable PGO and LTO.
2. The command "make" is ran once

Thank you,
Alecsandru

--
components: Build
files: cpython2_pgo_default-v01.patch
keywords: patch
messages: 260271
nosy: alecsandru.patrascu
priority: normal
severity: normal
status: open
title: CPython build options for out-of-the box performance
type: performance
versions: Python 2.7, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41918/cpython2_pgo_default-v01.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26359] CPython build options for out-of-the box performance

[Alecsandru Patrascu]

Changes by Alecsandru Patrascu :


Added file: http://bugs.python.org/file41919/cpython3_pgo_default-v02.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
nosy: +pitrou, serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24915] Profile Guided Optimization improvements (better training, llvm support, etc)

[Alecsandru Patrascu]

Changes by Alecsandru Patrascu :


Added file: http://bugs.python.org/file41917/pgofix-cpython3.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24915] Profile Guided Optimization improvements (better training, llvm support, etc)

[Alecsandru Patrascu]

Alecsandru Patrascu added the comment:

I've added a fix for the PGO builds after a issue pointed out in #26307. Thank 
you Christos for your observation!

--
Added file: http://bugs.python.org/file41916/pgofix-cpython2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26334] bytes.translate() doesn't take keyword arguments; docs suggests it does

[Martin Panter]

Martin Panter added the comment:

Nicholas, there is Issue 8706 about converting functions and methods to accept 
keywords in general.

There is also the slash “/” indicator proposed by PEP 457, which is used for 
some functions in pydoc; bytes.replace() for instance. In Issue 23738 I was 
trying to get some consensus on using this slash notation in the main 
documentation, in which case bytes.translate() could look like

bytes.translate(table, delete=b"", /)

And there is Issue 21314 about where to document the slash notation that is 
already used in pydoc.

--
nosy: +martin.panter
superseder:  -> accept keyword arguments on most base type methods and builtins

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26360] Deadlock in thread.join

[Mark Dickinson]

Mark Dickinson added the comment:

Build details: this was a version of Python built with a simple `./configure && 
make` from commit 32893d8a52a9.

taniyama:cpython mdickinson$ ./python.exe
Python 2.7.10+ (2.7:32893d8a52a9, Feb 14 2016, 11:08:14) 
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com