[Python-Dev] [RELEASE] ACTION REQUIRED: Python 3.8.0b4 now available for testing

2019-08-30 Thread Łukasz Langa 
It's time for the last beta release of Python 3.8. Go find it at:

https://www.python.org/downloads/release/python-380b4/ 



This release is the last of four planned beta release previews. Beta release 
previews are intended to give the wider community the opportunity to test new 
features and bug fixes and to prepare their projects to support the new feature 
release. The next pre-release of Python 3.8 will be 3.8.0c1, the first release 
candidate, currently scheduled for 2019-09-30.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.8 during the beta phase and report issues found to the Python bug tracker as 
soon as possible. Please note this is the last beta release, there is not much 
time left to identify and fix issues before the release of 3.8.0. If you were 
hesitating trying it out before, now is the time.

While the release is planned to be feature complete entering the beta phase, it 
is possible that features may be modified or, in rare cases, deleted up until 
the start of the release candidate phase (2019-09-30). Our goal is have no ABI 
changes after beta 3 and no code changes after 3.8.0c1, the release candidate.

To achieve that, it will be extremely important to get as much exposure for 3.8 
as possible during the beta phase. That beta phase is coming to an end. Please 
test now.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Acknowledgments

Many developers worked hard for the past four weeks to squash remaining bugs, 
some requiring non-obvious decisions. Many thanks to the most active, namely 
Raymond Hettinger, Steve Dower, Victor Stinner, Terry Jan Reedy, Serhiy 
Storchaka, Pablo Galindo Salgado, Tal Einat, Zackery Spytz, Ronald Oussoren, 
Neil Schemenauer, Inada Naoki, Christian Heimes, and Andrew Svetlov.

3.8.0 would not reach the Last Beta without you. Thank you!


- Ł


signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/AP7O65CDZWNWGCLJBRYLW3AP5H4L3MRK/

[Python-Dev] Summary of Python tracker Issues

2019-08-30 Thread Python tracker 

ACTIVITY SUMMARY (2019-08-23 - 2019-08-30)
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:
  open7114 (-39)
  closed 42626 (+97)
  total  49740 (+58)

Open issues with patches: 2864 


Issues opened (36)
==

#34410: itertools.tee not thread-safe; can segfault interpreter when w
https://bugs.python.org/issue34410  reopened by serhiy.storchaka

#37834: readlink on Windows cannot read app exec links
https://bugs.python.org/issue37834  reopened by lukasz.langa

#37932: ConfigParser.items(section) with allow_no_value returns empty 
https://bugs.python.org/issue37932  opened by Sean Robertson

#37935: Improve performance of pathlib.scandir()
https://bugs.python.org/issue37935  opened by Shai

#37936: gitignore file is too broad
https://bugs.python.org/issue37936  opened by Greg Price

#37937: Mention ``frame.f_trace`` in :func:`sys.settrace` docs.
https://bugs.python.org/issue37937  opened by cool-RR

#37938: refactor PyLong_As*() functions
https://bugs.python.org/issue37938  opened by sir-sigurd

#37939: os.path.normpath change some characters of a path into kinda '
https://bugs.python.org/issue37939  opened by Yugi

#37940: Add xml.tool to pretty print XML like json.tool
https://bugs.python.org/issue37940  opened by xtreak

#37941: python -m and runpy.run_module set different __name__ by defau
https://bugs.python.org/issue37941  opened by Julian

#37943: mimetypes.guess_extension() doesn’t get JPG right
https://bugs.python.org/issue37943  opened by _savage

#37945: test_locale failing
https://bugs.python.org/issue37945  opened by tim.golden

#37948: get_type_hints fails if there are un-annotated fields in a dat
https://bugs.python.org/issue37948  opened by arne

#37951: Disallow fork in a subinterpreter broke subprocesses in mod_ws
https://bugs.python.org/issue37951  opened by christian.heimes

#37952: Add support for export_keying_material to SSL library
https://bugs.python.org/issue37952  opened by wingel71

#37953: Fix ForwardRef equality checks
https://bugs.python.org/issue37953  opened by plokmijnuhby

#37955: mock.patch incorrect reference to Mock
https://bugs.python.org/issue37955  opened by phsilva

#37956: UUID authorize version 6+ with variant RFC 4122
https://bugs.python.org/issue37956  opened by Erawpalassalg

#37957: Allow regrtest to receive a file with test (and subtests) to i
https://bugs.python.org/issue37957  opened by pablogsal

#37958: Adding get_profile_dict to pstats
https://bugs.python.org/issue37958  opened by Daniel Olshansky

#37961: Tracemalloc traces do not include original stack trace length
https://bugs.python.org/issue37961  opened by jd

#37963: No URL for docs of pth files
https://bugs.python.org/issue37963  opened by Thomas Güttler

#37966: is_normalized is much slower at "no" than the standard's algor
https://bugs.python.org/issue37966  opened by Greg Price

#37967: release candidate is not gpg signed (and missing release workf
https://bugs.python.org/issue37967  opened by mattip

#37969: urllib.parse functions reporting false equivalent URIs
https://bugs.python.org/issue37969  opened by maggyero

#37970: urllib.parse docstrings incomplete
https://bugs.python.org/issue37970  opened by zach.ware

#37971: Wrong trace with multiple decorators (linenumber wrong in fram
https://bugs.python.org/issue37971  opened by control-k

#37972: unittest.mock.call does not chain __getitem__ to another _Call
https://bugs.python.org/issue37972  opened by blhsing

#37973: improve docstrings of sys.float_info
https://bugs.python.org/issue37973  opened by sir-sigurd

#37977: Big red pickle security warning should stress the point even m
https://bugs.python.org/issue37977  opened by lordmauve

#37980: regression when passing numpy bools to sorted(..., reverse=r)
https://bugs.python.org/issue37980  opened by tcaswell

#37981: Can't install Python 3.7.4 x64 on Win 8.1
https://bugs.python.org/issue37981  opened by Alexander Podgórski

#37985: WFERR_UNMARSHALLABLE breaks recursion limit
https://bugs.python.org/issue37985  opened by herring

#37986: Improve perfomance of PyLong_FromDouble()
https://bugs.python.org/issue37986  opened by sir-sigurd

#37988: Issue found during language name processing in a list
https://bugs.python.org/issue37988  opened by AjaySyam

#37989: documentation format error in Chinese version
https://bugs.python.org/issue37989  opened by 刘俨晖



Most recent 15 issues with no replies (15)
==

#37989: documentation format error in Chinese version
https://bugs.python.org/issue37989

#37986: Improve perfomance of PyLong_FromDouble()
https://bugs.python.org/issue37986

#37981: Can't install Python 3.7.4 x64 on Win 8.1
https://bugs.python.org/issue37981

#37977: Big red pickle security warning should stress the point even m
https://bugs.python.org/issue37977

#37972: unittest.mock.call does

[Python-Dev] Re: [python-committers] PEP 581/588 RFC: Collecting feedback about GitHub Issues

2019-08-30 Thread Raymond Hettinger 


> On Aug 27, 2019, at 10:44 AM, Mariatta  wrote:
> 
> (cross posting to python-committers, python-dev, core-workflow)
> 
> PEP 581: Using GitHub Issues has been accepted by the steering council, but 
> PEP 588: GitHub Issues Migration plan is still in progress.
> 
> I'd like to hear from core developers as well as heavy b.p.o users, the 
> following:
> 
>   • what features do they find lacking from GitHub issues, or
>   • what are the things you can do in b.p.o but not in GitHub, or
>   • Other workflow that will be blocked if we were to switch to GitHub 
> today
> By understanding your needs, we can be better prepared for the migration, and 
> we can start looking for solutions.

One other bit of workflow that would be blocked if there was a switch to GitHub 
today:

* On the tracker, we have long running conversations, sometimes spanning years. 
  We need to be able to continue those conversations even though the original 
participants may not have Github accounts (also, if they do have a Github 
account, we'll need to be able to link to the corresponding BPO account).  

* I believe some of the accounts are anonymous or have pseudonyms.  Am not sure 
how those can be migrated, we know very little about the participant except for 
their recurring posts.


Raymond


___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/MT2PJFS2CVDSWQKCCRUR3BCNXR4OSEKU/