Mailman 3 February 2021 - Python-announce-list

PyCA cryptography 3.3.2 and 3.4 released
by Paul Kehrer 07 Feb '21

07 Feb '21

PyCA cryptography 3.3.2 and 3.4 have been released to PyPI. cryptography includes both high level recipes and low level interfaces to common cryptographic algorithms such as symmetric ciphers, asymmetric algorithms, message digests, X509, key derivation functions, and much more. 3.3.2 supports Python 2.7, Python 3.6+, and PyPy, while 3.4 supports Python 3.6+ (including PyPy3). 3.3.2 Changelog (https://cryptography.io/en/latest/changelog.html#v3-3-2): * SECURITY ISSUE: Fixed a bug where certain sequences of update() calls when symmetrically encrypting very large payloads (>2GB) could result in an integer overflow, leading to buffer overflows. CVE-2020-36242 Please note 3.3.2 is the FINAL RELEASE supporting Python 2.7. 3.4 Changelog (https://cryptography.io/en/latest/changelog.html#v3-4) * BACKWARDS INCOMPATIBLE: Support for Python 2 has been removed. * We now ship manylinux2014 wheels and no longer ship manylinux1 wheels. Users should upgrade to the latest pip to ensure this doesn’t cause issues downloading wheels on their platform. cryptography now incorporates Rust code. Users building cryptography themselves will need to have the Rust toolchain installed. Users who use an officially produced wheel will not need to make any changes. The minimum supported Rust version is 1.45.0. * cryptography now has PEP 484 type hints on nearly all of of its public APIs. Users can begin using them to type check their code with mypy. -Paul Kehrer (reaperhulk)

1 0

ANN: Plumage 1.4.0; access trademark status info from USPTO
by Terry Carroll 05 Feb '21

05 Feb '21

I am pleased to announce Plumage (Plumage-py) 1.4.0 ("Experiment IV"). Plumage is a module to obtain trademark status and information from the United States Patent & Trademark Office's (USPTO's) Trademark Status & Document Retrieval (TSDR) system. It takes as input either a trademark registration number or application serial number, fetches the corresponding XML data from the PTO's TSDR website, and returns a dictionary of data associated with the specified TSDR entry. Example: from Plumage import plumage t = plumage.TSDRReq() t.setAPIKey(APIKEY) # API Key obtained from USPTO t.getTSDRInfo("2564831", "r") # get info on reg. no 2,564,831 tsdrdata=t.TSDRData if tsdrdata.TSDRMapIsValid: print("Application serial no: ", tsdrdata.TSDRSingle["ApplicationNumber"]) print("Trademark text: ", tsdrdata.TSDRSingle["MarkVerbalElementText"]) print("Application filing date: ", tsdrdata.TSDRSingle["ApplicationDate"]) print("Registration no: ", tsdrdata.TSDRSingle["RegistrationNumber"]) # Owner info is in most recent (0th) entry in ApplicantList applicant_list = tsdrdata.TSDRMulti["ApplicantList"] current_owner_info = applicant_list[0] print("Owner:", current_owner_info["ApplicantName"]) Will print: Application serial no: 75181334 Trademark text: MONTY PYTHON'S FLYING CIRCUS Application filing date: 1996-10-15-04:00 Registration no: 2564831 Owner: Python (Monty) Pictures Ltd. Multiple trademark applications or registrations can be successively queried. for example: t = plumage.TSDRReq() application_numbers = ["76535603", "75854426", "86142154", "78790815", "75533975"] for application_number in application_numbers: result = t.getTSDRInfo(application_number, "s") print(t.TSDRData.TSDRSingle["MarkVerbalElementText"]) Will display: NO BUDDY ESPEX ZA SPANISH INQUISITION New in this release: * Support for USPTO API key. The USPTO recently instituted a requirement that calls to TSDR require an API key, and the inability to specify one broke Plumage. This is now fixed. * By default, there is a one-second delay between TSDR calls, to comply with the USPTO policy limiting calls to 60/minute. The length of the delay can be modified by calling SetIntervalTime() (including setting the delay to zero if you want to manage the timing yourself). * By default, TSDR calls now default to requests for ST.96-format XML files. Prior to V1.4.0, the default was for ZIP files. The USPTO limit for zip files is tighter (4/minute) than for text XML (60/minute). The primary benefit of getting a zip file is that it includes the trademark specimen image. You porbably don't need it, but if you require image data, you can continue to request ZIP files by calling setPTOFormat("zip"). * New method GetMetainfo() allowing access to some metadata (not specific to a particular TSDR call) without a call to the USPTO TSDR server. * Additional status information about a particular mark is provided: - StaffName: the PTO staff member to whom a trademark is assigned - StaffOfficialTitle: the title of the assigned staff member - Three new lists are reported, to provide information on a mark's classification and dates of first use in each: - InternationalClassDescriptionList: provides information on international classification; - DomesticClassDescriptionList: provides information on domestic (US) classification; and - FirstUseDateList: provides information on dates of first use on a per-class basis * Some changes on reported metadata. * Support for Python 2 is DROPPED in this release. Release details: https://github.com/codingatty/Plumage-py/releases/tag/V1.4.0 Docs: https://github.com/codingatty/Plumage/wiki/Plumage-Home License: Apache Software License V2 -- Terry Carroll carroll(a)tjc.com

1 0

Python 3.10.0a5 is now available
by Pablo Galindo Salgado 03 Feb '21

03 Feb '21

Well, this one took a bit more time due to some surprise last time reference leaks and release blockers to fix, but now Python 3.10.0a5 it’s here. Will this be the first release announcement of the 3.10 series without copy-paste typos? Go get it here: https://www.python.org/downloads/release/python-3100a5/ *Major new features of the 3.10 series, compared to 3.9* Python 3.10 is still in development. This release, 3.10.0a5 is the fifth of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2021-05-03) and, if necessary, may be modified or deleted up until the release candidate phase (2021-10-04). Please keep in mind that this is a preview release and its use is not recommended for production environments. Many new features for Python 3.10 are still being planned and written. Among the new major new features and changes so far: - PEP 623 <https://www.python.org/dev/peps/pep-0623/> – Remove wstr from Unicode - PEP 604 <https://www.python.org/dev/peps/pep-0604/> – Allow writing union types as X | Y - PEP 612 <https://www.python.org/dev/peps/pep-0612/> – Parameter Specification Variables - PEP 626 <https://www.python.org/dev/peps/pep-0626/> – Precise line numbers for debugging and other tools. - bpo-38605 <https://bugs.python.org/issue38605>: from __future__ import annotations (PEP 563 <https://www.python.org/dev/peps/pep-0563/>) is now the default. - PEP 618 <https://www.python.org/dev/peps/pep-0618/>– Add Optional Length-Checking To zip. - bpo-12782 <https://bugs.python.org/issue12782>: Parenthesized context managers are now officially allowed. - (Hey, fellow core developer, if a feature you find important is missing from this list, let Pablo know <pablogsal(a)python.org>.) The next pre-release of Python 3.10 will be 3.10.0a6, currently scheduled for 2021-03-01. And now for something completely different The Chandrasekhar limit is the maximum mass of a stable white dwarf star. White dwarfs resist gravitational collapse primarily through electron degeneracy pressure, compared to main sequence stars, which resist collapse through thermal pressure. The Chandrasekhar limit is the mass above which electron degeneracy pressure in the star’s core is insufficient to balance the star’s own gravitational self-attraction. Consequently, a white dwarf with a mass greater than the limit is subject to further gravitational collapse, evolving into a different type of stellar remnant, such as a neutron star or black hole. Those with masses up to the limit remain stable as white dwarfs. The currently accepted value of the Chandrasekhar limit is about 1.4 M☉ (2.765×1030 kg). So we can be safe knowing that our sun is not going to become a black hole! Regards from cloudy London, Pablo Galindo Salgado

1 0