On Fri, Aug 24, 2018 at 1:22 PM Michael wrote:
>
> I am trying to be a 'good scout' and run "make patchcheck" more
> regularly. However, I generally am not successful because I build and
> test in separate directories.
There is an open issue about supporting out-of-tree builds:
https://bugs.pytho
I don't quite understand the problem you're facing with git and make
patchcheck?
Also, perhaps this is more for core-workflow instead of python-dev.
Mariatta
ᐧ
On Fri, Aug 24, 2018 at 3:20 AM Michael wrote:
> I am trying to be a 'good scout' and run "make patchcheck" more
> regularly. However
ACTIVITY SUMMARY (2018-08-17 - 2018-08-24)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open6807 (+31)
closed 39431 (+36)
total 46238 (+67)
Open issues wi
I am trying to be a 'good scout' and run "make patchcheck" more
regularly. However, I generally am not successful because I build and
test in separate directories.
There is access to git! just no ready reference in the build area.
So, not calling it a bug - but if someone else also experiences th
On 8/23/2018 2:53 PM, Collin Anderson wrote:
Hi All,
Sorry if this has been mentioned before, but I noticed the Python 2.7
EOL date was recently set to Jan 1st, 2020.
My understanding was Python releases get 5 years of support from their
initial release,
'5' is a rounded, rather than exact
On 8/23/2018 8:14 PM, Barry Warsaw wrote:
On Aug 23, 2018, at 15:23, Eric V. Smith wrote:
On 8/23/2018 4:30 PM, Victor Stinner wrote:
Hi,
The reference is the PEP 373 "Python 2.7 Release Schedule". See the
"Update" section:
https://www.python.org/dev/peps/pep-0373/#update
We could probably
