[Python-Dev] Re: Test error

2022-03-03 Thread Terry Reedy 

On 3/3/2022 3:09 PM, Brett Cannon wrote:
You might want to try asking your question at 
 
which is specifically set up to help people.


But in general, all the tests are passing for folks. You will need to 
run those tests individually to see why they are failing for you.


On Thu, Mar 3, 2022 at 12:01 PM > wrote:



2 tests failed:
     test_compileall test_distutils



Sometimes tests that pass on CI or buildbots fail on a person's 
repository build or the most recent installed python.  However, on my 
Win10 machine, both tests pass on a recent main (3.11.0a5+) build and on 
installed 3.11.0a5.


If you rerun
  python -m test -v test_compileall test_distutils
where 'python' starts either a repository debug build of main or an 
installed 3.11.0a5 (installers available for Windows and macOS), I 
suggest you post to

https://mail.python.org/mailman/listinfo/python-list
with complete details on your system and relevant parts of the 'verbose' 
output.  Use 'test_xyz failure on ' as the subject so people with 
knowledge of the module or OS are more likely to read it.


--
Terry Jan Reedy
___
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/DPLXPKADZWYJBQ3RSSHM6JHNOBQWG3MC/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Defining tiered platform support

2022-03-03 Thread Brett Cannon 
Do we officially support NetBSD? Do you know how to find out if we do? You
might think to look at
https://www.python.org/dev/peps/pep-0011/#supporting-platforms , but that
just loosely defines the criteria and it still doesn't list the actual
platforms we support. (BTW I don't know if we do officially support NetBSD,
hence this email.)

I think we should clarify this sort of thing and be a bit more upfront with
the level of support we expect/provide for a platform. As such, I want to
restructure PEP 11 to list the platforms we support, not just list the
platforms we stopped supporting. To do this I want define 3 different tiers
that outline what our support requirements and promises are for platforms.

Tier 1 is the stuff we run CI against: latest Windows, latest macOS, Linux
w/ the latest glibc (I don't know of a better way to define Linux support
as I don't know if a per-distro list is the right abstraction). These are
platforms we won't even let code be committed for if they would break; they
block releases if they don't work. These platforms we all implicitly
promise to support.

Tier 2 is the platforms we would revert a change within 24 hours if they
broke: latest FeeBSD, older Windows, older macOS, Linux w/ older glibc.This
is historically the "stable buildbot plus a core dev" group of platforms.
The change I would like to see is two core devs (in case one is on
vacation), and a policy as to how a platform ends up here (e.g. SC must
okay it based on consensus of everyone). The stable buildbot would still be
needed to know if a release is blocked as we would hold a release up if
they were red. The platform and the core devs supporting these platforms
would be listed in PEP 11.

Tier 3 are platforms we accept PRs for to keep working, but they won't
block a release. At least one core dev must be listed to be in charge of
PRs that affect the platform. A buildbot would be nice but not required.
I'm thinking either historical platforms we support or something like
Emscripten that's working towards being a tier 2 platform. I'm not sure if
we want to have explicit approval to be in this tier beyond the outlined
requirements, but obviously if a core dev isn't keeping up with PRs then
the platform will be dropped.

All other platforms we do not directly support in the repository and it is
up to the community to keep functioning. We can obviously keep accepting
general patches to up compatibility, but platform-specific patches for
anything outside of these tiers wouldn't. No issue if someone provides a
buildbot for their own benefit, but these buildbots would never hold
anything up.

When a Python version hits b1, then that platform is considered supported
for that version as long as the requirements outlined above continue to be
met. Once the Python version hits EOL then like anything, support ends no
matter what. We could capture the supported platforms for a version in the
release schedule PEP if people want.

I would expect appropriate labels being added to the builders listed at
https://buildbot.python.org/all/#/builders to signify which platforms we
block releases for (e.g. `tier-1,`, `tier-2`, or `release-blocker` as a
generic label).

I would expect PEP 11 to list the appropriate C symbol that's set for that
platform, e.g. __linux__.

I don't know if we want to bother listing CPU architectures since we are a
pure C project which makes CPU architecture less of a thing, but I'm
personally open to the idea of CPU architectures being a part of the
platform definition.

I don't think we should cover C compilers here as that's covered by PEP 7.
Otherwise PEP 7 should only list C versions/features and PEP 11 lists
compilers and their versions.

FYI the tier support idea and the rough definitions above come from Rust:
https://doc.rust-lang.org/nightly/rustc/platform-support.html .
___
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/ZPBSHENP3V7KHNPYWE6BEQD5ASES2NLV/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Re: Python 3.11.0a6 is blocked

2022-03-03 Thread Victor Stinner 
By the way, AMD64 Arch Linux Usan 3.x started failing because I
enabled more tests on this buildbot yesterday.

Previously, "test_faulthandler test_hashlib test_concurrent_futures
test_ctypes" were simply skipped on this UBSAN buildbot.

I'm working on fixing the 3 failing tests: test_ctypes,
test_faulthandler and test_hashlib
https://bugs.python.org/issue46913

So it's not a regression, it's just that the buildbot became stricter.

Victor
___
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/G7JH45WMFY3NNWXH3N4OERT62HVOAMCT/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Test error

2022-03-03 Thread Brett Cannon 
You might want to try asking your question at
https://mail.python.org/mailman3/lists/core-mentorship.python.org/ which is
specifically set up to help people.

But in general, all the tests are passing for folks. You will need to run
those tests individually to see why they are failing for you.

On Thu, Mar 3, 2022 at 12:01 PM  wrote:

> I am new to open source and think to contribute to python .
> I was going through the developer guide and when i run this code "./python
> -m test -j3" on my terminal i got this result which say it fail .Now can
> someone tell me this is normal or happning to me only . If this happen to
> everyone how can i fix this
> == Tests result: FAILURE ==
> 380 tests OK.
> 2 tests failed:
> test_compileall test_distutils
> 43 tests skipped:
> test_asdl_parser test_check_c_globals test_clinic test_curses
> test_dbm_gnu test_dbm_ndbm test_devpoll test_epoll test_fcntl
> test_fork1 test_gdb test_grp test_ioctl test_kqueue
> test_multiprocessing_fork test_multiprocessing_forkserver test_nis
> test_openpty test_ossaudiodev test_pipes test_poll test_posix
> test_pty test_pwd test_readline test_resource test_smtpnet
> test_socketserver test_spwd test_syslog test_threadsignals
> test_timeout test_tix test_tk test_ttk_guionly test_urllib2net
> test_urllibnet test_wait3 test_wait4 test_winsound test_xmlrpc_net
> test_xxtestfuzz test_zipfile64
> Total duration: 11 min 14 sec
> Tests result: FAILURE
> ___
> 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/HLNULX74RBEQ5ZKVTZBT4FYTZGT7JET2/
> Code of Conduct: http://python.org/psf/codeofconduct/
>
___
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/4FYW7MIRJ2D6PRETBCE3JVGRMQ67HPTS/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Test error

2022-03-03 Thread sachin1122621003 
I am new to open source and think to contribute to python .
I was going through the developer guide and when i run this code "./python -m 
test -j3" on my terminal i got this result which say it fail .Now can someone 
tell me this is normal or happning to me only . If this happen to everyone how 
can i fix this 
== Tests result: FAILURE ==
380 tests OK.
2 tests failed:
test_compileall test_distutils
43 tests skipped:
test_asdl_parser test_check_c_globals test_clinic test_curses
test_dbm_gnu test_dbm_ndbm test_devpoll test_epoll test_fcntl
test_fork1 test_gdb test_grp test_ioctl test_kqueue
test_multiprocessing_fork test_multiprocessing_forkserver test_nis
test_openpty test_ossaudiodev test_pipes test_poll test_posix
test_pty test_pwd test_readline test_resource test_smtpnet
test_socketserver test_spwd test_syslog test_threadsignals
test_timeout test_tix test_tk test_ttk_guionly test_urllib2net
test_urllibnet test_wait3 test_wait4 test_winsound test_xmlrpc_net
test_xxtestfuzz test_zipfile64
Total duration: 11 min 14 sec
Tests result: FAILURE
___
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/HLNULX74RBEQ5ZKVTZBT4FYTZGT7JET2/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Python 3.11.0a6 is blocked

2022-03-03 Thread Pablo Galindo Salgado 
Update: Seems that the refleaks have been fixed by Inada-san in this commit:

https://github.com/python/cpython/commit/3241cba4ec55ef0b9e73bf7a5a77ef29ae4b8756

I will wait until the buildbots are green and then try to proceed with the
release.

Thanks!

On Thu, 3 Mar 2022 at 20:14, Pablo Galindo Salgado 
wrote:

> Hi everyone,
>
> Unfortunately, the release of 3.11.0a6 is still blocked because all
> reflect buildbots are failing:
>
> https://buildbot.python.org/all/#/release_status
>
> I will try to identify the commit(s) that introduced the regression and
> revert them, but for the
> time being the release is on hold, sadly.
>
> Regards from rainy Salamanca,
> Pablo Galindo Salgado
>
> On Wed, 2 Mar 2022 at 14:52, Pablo Galindo Salgado 
> wrote:
>
>> Hi everyone,
>>
>> Unfortunately, we have some issues marked as release blockers that are
>> holding the 3.11.0a6 release.
>> Some of these issues have been solved but we still have a couple of them.
>> Hopefully, we will solve these
>> soon and I will proceed with the release.
>>
>> Thanks for your understanding.
>>
>> Regards from sunny Salamanca,
>> Pablo Galindo Salgado
>>
>
___
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/HO62U6PSAAJTLBMN2PH7ZNXFJK5IXBRF/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Python 3.11.0a6 is blocked

2022-03-03 Thread Pablo Galindo Salgado 
Hi everyone,

Unfortunately, the release of 3.11.0a6 is still blocked because all reflect
buildbots are failing:

https://buildbot.python.org/all/#/release_status

I will try to identify the commit(s) that introduced the regression and
revert them, but for the
time being the release is on hold, sadly.

Regards from rainy Salamanca,
Pablo Galindo Salgado

On Wed, 2 Mar 2022 at 14:52, Pablo Galindo Salgado 
wrote:

> Hi everyone,
>
> Unfortunately, we have some issues marked as release blockers that are
> holding the 3.11.0a6 release.
> Some of these issues have been solved but we still have a couple of them.
> Hopefully, we will solve these
> soon and I will proceed with the release.
>
> Thanks for your understanding.
>
> Regards from sunny Salamanca,
> Pablo Galindo Salgado
>
___
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/L5HIYXRWAL7YPM7WIHBRFJ4GG4IVJ6LI/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Improvements to the sys.path initialization documentation

2022-03-03 Thread Victor Stinner 
Hi,

I tried to document inputs and outputs of Modules/getpath.py in the C
API Initialization API:
https://docs.python.org/dev/c-api/init_config.html#python-path-configuration

I don't know if it would be possible to merge most of these
information at a single place to avoid oudated documentation.

Victor

On Wed, Mar 2, 2022 at 5:40 PM Russel Webber  wrote:
>
> Hi All,
>
> Steve Dower, Eryk Sun and I have been working on improving the documentation 
> around how sys.path is initialised and therefore how Python modules are found.
>
> We're moving the details from 
> https://docs.python.org/3.11/using/windows.html#finding-modules
> to a platform-agnostic new section in 
> https://docs.python.org/3.11/using/cmdline.html
>
> We're aiming to have one place in the documentation where all the ways to 
> customize sys.path (PYTHONPATH, ._pth, site, etc) are at least mentioned.
>
> We'd appreciate further community feedback on the changes before they are 
> merged.
> https://bugs.python.org/issue31582
> https://github.com/python/cpython/pull/31082
>
> Thank you,
> Russel
>
> ___
> 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/5AZQZH45EUCYN26SVD5DO6O7XTPSTIB5/
> Code of Conduct: http://python.org/psf/codeofconduct/



-- 
Night gathers, and now my watch begins. It shall not end until my death.
___
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/Q5VGOJPJE67JKCMZO2CZBH6UFM7EMXDY/
Code of Conduct: http://python.org/psf/codeofconduct/