Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
On 17 July 2015 at 01:49, Meador Inge wrote: > On Thu, Jul 16, 2015 at 10:08 AM, Nick Coghlan wrote: >> Given the global nature of the lists, I think we should be giving >> folks *at least* 24 hours to reply to a question before assuming >> they're not going to respond, and given that only some of us get to >> count reading and replying to python-dev threads as work time, a few >> days leeway would be better (perhaps even a week to account for folks >> that are busy with other things during the week and mostly contribute >> on weekends). Those of us that *do* get paid for this also need to try >> to remember to account for that asymmetry in available time for >> participation. > > To me this depends on why the change is being questioned. If there is > a question about why a change was made or a minor bug was found in > post-commit review*, then I agree it can wait a few days. On the other > hand, if someone commits a change that turns all the build-bots red and > doesn't respond for several hours, then I would think that is fair game > to revert. > > So, I do think reverting changes is a very reasonable course of action at > times. It should just be used judiciously. I agree. The problem at the moment is that the norms around various things (particularly relating to pre-commit and post-commit review) are not only largely unwritten but have also changed over time, so we sometimes get mismatched expectations. Longer term, there are actually some real tooling problems worth fixing (hence the forge.python.org proposals, and the core workflow GSoC projects), but a bit more clarity in our expectations wouldn't hurt in the meantime. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
[python-committers] 2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules
This failure happens only in 2.7 branch in the source tree. [localhost 2.7]$ hg branch 2.7 [localhost 2.7]$ hg head 2.7 changeset: 96916:ca78b9449e04 branch: 2.7 user:Zachary Ware date:Thu Jul 16 00:24:48 2015 -0500 $./configure is OK $ make /opt/twitter/bin/gcc-4.2 -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -o Python/mactoolboxglue.o Python/mactoolboxglue.c In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:55, from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20, from Include/pymactoolbox.h:10, from Python/mactoolboxglue.c:27: /System/Library/Frameworks/CoreServices.framework/Frameworks/FSEvents.framework/Headers/FSEvents.h:486: error: expected ‘,’ or ‘}’ before ‘__attribute__’ make: *** [Python/mactoolboxglue.o] Error 1 If I disable Mac specific modules $ ./configure --disable-toolbox-glue $ make is fine. Has any else observed this? I am trying to determine if this a bug or an incompatibility of Mac Command Line Tools I have with the 2.7 sources, most likely it is the later. -- Senthil ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules
On the road in the wilds of the Rockies at the moment I can check tonight but it should work. What version of OS X and Xcode :(xcodebuild -version)? -- Ned Deily > On Jul 17, 2015, at 10:21, Senthil Kumaran wrote: > > This failure happens only in 2.7 branch in the source tree. > > [localhost 2.7]$ hg branch > 2.7 > > [localhost 2.7]$ hg head 2.7 > changeset: 96916:ca78b9449e04 > branch: 2.7 > user:Zachary Ware > date:Thu Jul 16 00:24:48 2015 -0500 > > $./configure > > is OK > > $ make > /opt/twitter/bin/gcc-4.2 -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv > -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -o > Python/mactoolboxglue.o Python/mactoolboxglue.c > In file included from > /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:55, > from > /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20, > from Include/pymactoolbox.h:10, > from Python/mactoolboxglue.c:27: > /System/Library/Frameworks/CoreServices.framework/Frameworks/FSEvents.framework/Headers/FSEvents.h:486: > error: expected ‘,’ or ‘}’ before ‘__attribute__’ > make: *** [Python/mactoolboxglue.o] Error 1 > > > If I disable Mac specific modules > > $ ./configure --disable-toolbox-glue > $ make is fine. > > Has any else observed this? I am trying to determine if this a bug or an > incompatibility of Mac Command Line Tools I have with the 2.7 sources, most > likely it is the later. > > -- > Senthil > > > > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules
I am on 10.10.4 - Yosemite $ xcodebuild -version Xcode 6.1.1 Build version 6A2008a On Fri, Jul 17, 2015 at 9:44 AM, Ned Deily wrote: > On the road in the wilds of the Rockies at the moment I can check tonight > but it should work. What version of OS X and Xcode :(xcodebuild -version)? > > -- > Ned Deily > > > On Jul 17, 2015, at 10:21, Senthil Kumaran wrote: > > This failure happens only in 2.7 branch in the source tree. > > [localhost 2.7]$ hg branch > 2.7 > > [localhost 2.7]$ hg head 2.7 > changeset: 96916:ca78b9449e04 > branch: 2.7 > user:Zachary Ware > date:Thu Jul 16 00:24:48 2015 -0500 > > $./configure > > is OK > > $ make > /opt/twitter/bin/gcc-4.2 -c -fno-strict-aliasing -g -O2 -DNDEBUG -g > -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include > -DPy_BUILD_CORE -o Python/mactoolboxglue.o Python/mactoolboxglue.c > In file included from > /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:55, > from > /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20, > from Include/pymactoolbox.h:10, > from Python/mactoolboxglue.c:27: > /System/Library/Frameworks/CoreServices.framework/Frameworks/FSEvents.framework/Headers/FSEvents.h:486: > error: expected ‘,’ or ‘}’ before ‘__attribute__’ > make: *** [Python/mactoolboxglue.o] Error 1 > > > If I disable Mac specific modules > > $ ./configure --disable-toolbox-glue > $ make is fine. > > Has any else observed this? I am trying to determine if this a bug or an > incompatibility of Mac Command Line Tools I have with the 2.7 sources, most > likely it is the later. > > -- > Senthil > > > > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules
On Fri, Jul 17, 2015 at 11:21 AM, Senthil Kumaran wrote: > This failure happens only in 2.7 branch in the source tree. > > [localhost 2.7]$ hg branch > 2.7 > > [localhost 2.7]$ hg head 2.7 > changeset: 96916:ca78b9449e04 > branch: 2.7 > user:Zachary Ware > date:Thu Jul 16 00:24:48 2015 -0500 > > $./configure > > is OK > > $ make > /opt/twitter/bin/gcc-4.2 -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv > -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE > -o Python/mactoolboxglue.o Python/mactoolboxglue.c > In file included from > /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:55, > from > /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20, > from Include/pymactoolbox.h:10, > from Python/mactoolboxglue.c:27: > /System/Library/Frameworks/CoreServices.framework/Frameworks/FSEvents.framework/Headers/FSEvents.h:486: > error: expected ‘,’ or ‘}’ before ‘__attribute__’ > make: *** [Python/mactoolboxglue.o] Error 1 Are you really meaning to use GCC 4.2 (that is ancient)? I can reproduce your problem, but only with gcc-4.2. Clang works just fine. Here are the compiler versions I am using: drago:llvm meadori$ gcc-4.2 --version couldn't understand kern.osversion `14.3.0' i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. drago:llvm meadori$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix Hope that helps, -- Meador ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
Hi Nick, Given the amount of ludicrous babble that goes on on python-dev and the like, I've unsubscribed from those lists, so I don't have much interest in this discussion anymore. I hope you can make them a better place anyway. Regards Antoine. Le 15/07/2015 04:29, Nick Coghlan a écrit : > Hi folks, > > The FreeBSD community recently posted their Code of Conduct guidelines > for technical discussions at > https://www.freebsd.org/internal/code-of-conduct.html > > I think their guidelines align pretty well with the way we try to run > the CPython issue tracker and the core mailing lists, but we don't > currently spell out those expectations for newcomers (or potential > newcomers) as clearly as they have. > > Would folks mind if I drafted a CPython Code of Conduct inspired by > their example, and proposed it for inclusion in the Developer's Guide? > > Regards, > Nick. > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules
On Jul 17, 2015, at 13:26, Meador Inge wrote: > On Fri, Jul 17, 2015 at 11:21 AM, Senthil Kumaran wrote: >> This failure happens only in 2.7 branch in the source tree. >> >> [localhost 2.7]$ hg branch >> 2.7 >> >> [localhost 2.7]$ hg head 2.7 >> changeset: 96916:ca78b9449e04 >> branch: 2.7 >> user:Zachary Ware >> date:Thu Jul 16 00:24:48 2015 -0500 >> >> $./configure >> >> is OK >> >> $ make >> /opt/twitter/bin/gcc-4.2 -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv >> -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE >> -o Python/mactoolboxglue.o Python/mactoolboxglue.c >> In file included from >> /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:55, >> from >> /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20, >> from Include/pymactoolbox.h:10, >> from Python/mactoolboxglue.c:27: >> /System/Library/Frameworks/CoreServices.framework/Frameworks/FSEvents.framework/Headers/FSEvents.h:486: >> error: expected ‘,’ or ‘}’ before ‘__attribute__’ >> make: *** [Python/mactoolboxglue.o] Error 1 > > Are you really meaning to use GCC 4.2 (that is ancient)? > > I can reproduce your problem, but only with gcc-4.2. > Clang works just fine. > Here are the compiler versions I am using: > > drago:llvm meadori$ gcc-4.2 --version > couldn't understand kern.osversion `14.3.0' > i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) > Copyright (C) 2007 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > drago:llvm meadori$ gcc --version > Configured with: > --prefix=/Applications/Xcode.app/Contents/Developer/usr > --with-gxx-include-dir=/usr/include/c++/4.2.1 > Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) > Target: x86_64-apple-darwin14.3.0 > Thread model: posix > > Hope that helps, Meador's right. Don't use the old gcc-4.2 with the current SDK / Command Line Tools. Let CC default to "cc" or set it to "clang"; presumably something is setting the CC environment variable to /opt/twitter/bin/gcc-4.2. -- Ned Deily [email protected] -- [] ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
