-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.9.0rc recipe #389
Conversation
…nda-forge-pinning 2020.09.16.18.10.04
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
recipe/meta.yaml
Outdated
- patches/0012-Fix-find_library-so-that-it-looks-in-sys.prefix-lib-.patch | ||
- patches/0013-Disable-new-dtags-in-unixccompiler.py.patch | ||
- patches/0014-Fix-cross-compilation-on-Debian-based-distros.patch | ||
# - patches/0015-Disable-registry-lookup-unless-CONDA_PY_ALLOW_REG_PA.patch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mingwandroid this is inside a if (!Py_IgnoreEnvironmentFlag)
now. Does that solve our problem or do we still need to refresh this patch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I highly recommend keeping this. Without it, installers will fail, for example. We don't set Py_IgnoreEnvironmentFlag
and until we do (if we want to) and get this enforced in all the places we need to this is crucial.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I am not sure. I mean, this is our own var that some may have used.. if no one is using it then yeah, let's drop it.
@ocefpaf No worries; we're all busy. Thanks for looking into it. If not this release, there will always be a new one 😉 |
2888305
to
6220041
Compare
@mingwandroid all the patches are refreshed. It looks like we can drop Do you have an idea of which ones we should prioritize and try to push upstream? I'll investigate the Windows failure later, not sure what is going on. Linux and macOS are building correctly, the problem seems to be the lack of |
Hey @ocefpaf, My thoughts on upstreaming/dropping, patch-by-patch.. https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0000-Fix-off-by-one-error-in-_winapi_WaitForMultipleObjec.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0001-Add-Anaconda-Distribution-version-logic.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0002-Darwin-Add-arch-x86_64-to-UnicCCompiler-ld_args.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0003-Win32-Change-FD_SETSIZE-from-512-to-2048.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0004-Win32-distutils-Add-support-to-cygwinccompiler-for-V.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0005-Do-not-pass-g-to-GCC-when-not-Py_DEBUG.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0006-Support-cross-compiling-byte-code.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0007-Win32-Fixes-for-Windows-GCC-interop-needed-by-RPy2-a.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0008-Darwin-Look-in-sysroot-usr-lib-include-if-sysroot-is.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0009-runtime_library_dir_option-Use-1st-word-of-CC-as-com.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0010-Win32-Do-not-download-externals.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0011-Add-support-for-_CONDA_PYTHON_SYSCONFIGDATA_NAME-if-.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0012-Fix-find_library-so-that-it-looks-in-sys.prefix-lib-.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0013-Disable-new-dtags-in-unixccompiler.py.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0014-Fix-cross-compilation-on-Debian-based-distros.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0015-Disable-registry-lookup-unless-CONDA_PY_ALLOW_REG_PA.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0016-Unvendor-openssl.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0018-venv-Revert-a-change-from-https-jackfan.us.kg-python-cp.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0019-Win-Add-back-the-DLLSuffix-used-to-find-the-openssl-.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0020-Use-ranlib-from-env-if-env-variable-is-set.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0021-roll-back-2e33ecd-for-py_compile.main.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0022-Add-CondaEcosystemModifyDllSearchPath.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0023-Add-d1trimfile-SRC_DIR-to-make-pdbs-more-relocatable.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0024-Doing-d1trimfile.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0025-egg-debugging-with-Windows-debug-builds.patch https://github.com/AnacondaRecipes/python-feedstock/blob/master/recipe/patches/0026-Revert-part-of-https-bugs.python.org-issue33895-http.patch So we need a plan of attack. I'm more than happy to ask for time to be set aside for me to handle pushing these, starting with the easy ones first and seeing how far I go, but anyone is (always) welcome to propose any of my patches and ping me in the comments if they wish. |
I used AnacondaRecipes URLs in my last comment, sorry about that, but it's to make it easier for me when/if I tackle this. |
@mingwandroid, this is already fixed upstream, see bug report and fix python/cpython#17134. Actually, that specific patch isn't in 3.9.0rc1, but I've checked the contents of that tarball and the bug that my patch fixed isn't there, so this one can be dropped either way. |
@mingwandroid thnaks for the compilation of the patch status. @duncanmmacleod indeed the 0021-roll-back-2e33ecd-for-py_compile.main.patch seems to be in, I commented it out and I'm planning of removing it next iteration. I'm copying #389 (comment) in a doc so we can tackle one at a time. We already have @willingc 👀 here ;-p |
@zooba may want to take a look too? |
The test error is because of a |
recipe/meta.yaml
Outdated
- ripgrep | ||
- cmake | ||
- ninja | ||
- setuptools |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ocefpaf, need to remove this too
recipe/meta.yaml
Outdated
- pushd distutils.cext | ||
- python setup.py install -v -v | ||
- python -c "import greet; greet.greet('Python user')" | rg "Hello Python" | ||
- popd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These 4 lines too
Rather than removing all these tests, can you elide them when the patch number is 0? I think that way, we can do a build 1 once the necessary deps are present and get the benefits of the tests back. |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
This builds now. What's the plan with tzdata though? |
Does anyone know why the linter is complaining? Each output has build/number: 0 now. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
This doesn't address the tzdata thing. We can do that in a follow up PR? |
@mingwandroid are you OK pointing this to the rc label, switching to the rc2, and merging it there first? That way we can wait for the tzdata stuff and prepare this for master in another PR. |
@mingwandroid awesome work! We will merge this in the rc label for now, without the tzdata, and I'll port this recipe to |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
Nice. Thanks |
xref #270. @willingc You opened it but we never addressed this properly. The main issue is bandwidth to catch up with upstream, even if that will happen only on the RCs. I'm investigating the patches here and I hope to be able to work with upstream to see if we can get some of them merged (or dropped for something better).