[python-committers] Official way to check out a tag?
Hello, what is the official way to checkout a tag for debugging? I did: git checkout v3.6.0 This just worked in mercurial, but doing the above results in a compile error: threadmodule.c:1355: multiple definition of `PyInit__thread' Stefan Krah ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Official way to check out a tag?
Le 23/01/2018 à 11:28, Stefan Krah a écrit : > > Hello, > > what is the official way to checkout a tag for debugging? I did: > >git checkout v3.6.0 > > > This just worked in mercurial, but doing the above results in a > compile error: > >threadmodule.c:1355: multiple definition of `PyInit__thread' Did you try "make distclean"? Regards Antoine. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Official way to check out a tag?
On Tue, Jan 23, 2018 at 11:29:49AM +0100, Antoine Pitrou wrote: > > This just worked in mercurial, but doing the above results in a > > compile error: > > > >threadmodule.c:1355: multiple definition of `PyInit__thread' > > Did you try "make distclean"? Thanks, that works! I assumed that I mishandled git and completely overlooked the easier solution. :-) Stefan Krah ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Official way to check out a tag?
2018-01-23 11:29 GMT+01:00 Antoine Pitrou : > Did you try "make distclean"? Oh by the way, it took me year to discover the cool *builtin* Git function: * "git clean -ndx" shows all untracked files and directories * "git clean -fdx" removes all untracked files and directories BE CAREFUL: "git clean -fdx" really removes anything not tracked by Git, including your local files and all your local directories. You may use "make clean" or even "make distclean" before "git clean -ndx" to better see what will be removed. In short, "git clean -fdx" *behaves* as "cd ..; rm -rf python; git clone https://github.com/python/cpython python; cd python", without the need to download everything again ;-) When I have a local patch like test.patch, I move it to the parent directory, run git clean, and move back the file. Victor ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] [RELEASED] Python 3.4.8rc1 and Python 3.5.5rc1 are now available
On behalf of the Python development community, I'm pleased to announce the availability of Python 3.4.8rc1 and Python 3.5.5rc1. Both Python 3.4 and 3.5 are in "security fixes only" mode. Both versions only accept security fixes, not conventional bug fixes, and both releases are source-only. You can find Python 3.4.8rc1 here: https://www.python.org/downloads/release/python-348rc1/ And you can find Python 3.5.5rc1 here: https://www.python.org/downloads/release/python-355rc1/ Happy Pythoning, //arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
