On 7/21/2015 6:20 PM, Vitale, Joseph wrote:
Hello,
Trying to install Python 3.4.3 on Red Hat 6.6 zLinux(s390x) but
“make” fails and core dumps. Not using OpenSSL and did not configure
for it.
Questions about installing current Python should be directed to
python-list. pydev is for develo
On 7/21/15 9:31 PM, Nick Coghlan wrote:
On 22 July 2015 at 04:08, Brett Cannon wrote:
On Tue, Jul 21, 2015 at 11:05 AM Carol Willing
wrote:
The Communications Quick Start section would be brief and practical much
like the Quick Start section for downloading and testing the source
code. Placin
On 22 July 2015 at 13:23, Nikolaus Rath wrote:
> If it were up to me, I'd focus all the resources of the PSF on reducing
> this backlog - be that by hiring some core developers to work full-time
> on just the open bugtracker issues, or by financing development of
> better code review and commit in
On 22 July 2015 at 04:08, Brett Cannon wrote:
> On Tue, Jul 21, 2015 at 11:05 AM Carol Willing
> wrote:
>> The Communications Quick Start section would be brief and practical much
>> like the Quick Start section for downloading and testing the source
>> code. Placing the Communications Quick Star
On Jul 21 2015, Nick Coghlan wrote:
> All of this is why the chart that I believe should be worrying people
> is the topmost one on this page:
> http://bugs.python.org/issue?@template=stats
>
> Both the number of open issues and the number of open issues with
> patches are steadily trending upward
Nick Coghlan writes:
> The draining and demotivating cases are the ones where *no new
> information is introduced*, but the design decision is *challenged
> anyway*.
But this particular thread is an extreme case, that demonstrates why
this kind of thing happens *despite* the good intentions of
Ben Finney writes:
> Definitely agreed, and I'm not implying otherwise.
>
> There is a distinction to be drawn:
>
> * If challenged to do so, could one (the contributor) present a
> compelling justification for the change?
Aside from Paul's disclaimer, this is way too high a bar. Nick
Hello,
Trying to install Python 3.4.3 on Red Hat 6.6 zLinux(s390x) but "make" fails
and core dumps. Not using OpenSSL and did not configure for it.
Can you provide direction?
./configure
make
gcc -pthread -fPIC -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
-Werror=declaration-afte
On 22 July 2015 at 05:08, Larry Hastings wrote:
>
>
> On 07/21/2015 06:35 PM, Robert Collins wrote:
>
> Cool. http://bugs.python.org/issue21750 is in a bad state right now.
>
> I landed a patch to fix it, which when exposed to users had some
> defects. I'm working on a better patch now, but need t
On 7/21/2015 1:06 PM, Carol Willing wrote:
I would like to add a "Communications Quick Start" section to the
beginning of the Python Developer's Guide.
I would rename 'Quick Start' to 'Quick Start: Code Development' and add
'Quick Start: Communications' (or maybe 'Q S: Community Interaction').
On Tue, Jul 21, 2015 at 11:05 AM Carol Willing <
willi...@willingconsulting.com> wrote:
> I would like to add a "Communications Quick Start" section to the
> beginning of the Python Developer's Guide.
>
> Productive communication between each other will always be critical to
> future development o
I would like to add a "Communications Quick Start" section to the
beginning of the Python Developer's Guide.
Productive communication between each other will always be critical to
future development of CPython and maintaining releases, infrastructure,
documentation, and more.
Unproductive co
On 07/21/2015 06:35 PM, Robert Collins wrote:
Cool. http://bugs.python.org/issue21750 is in a bad state right now.
I landed a patch to fix it, which when exposed to users had some
defects. I'm working on a better patch now, but need to either roll
the prior patch completely back, or get the ne
Cool. http://bugs.python.org/issue21750 is in a bad state right now.
I landed a patch to fix it, which when exposed to users had some
defects. I'm working on a better patch now, but need to either roll
the prior patch completely back, or get the new one landed before the
next beta. I hope to have
On 22 July 2015 at 03:47, Tim Golden wrote:
> On 20/07/2015 19:48, Christie Wilson wrote:
>> I am terrified of replying to this thread since so many folks on it seem
>> unhappy that it is continuing, but I want to +1 what Erik said.
>
> Don't be terrified :)
>
> But do understand that, in general,
On 21 July 2015 at 19:40, Nick Coghlan wrote:
> On 20 July 2015 at 22:34, Ben Finney wrote:
>> Paul Moore writes:
>>
>>> Again, I'm sorry to pick on one sentence out of context, but it cut
>>> straight to my biggest fear when doing a commit (on any project) -
>>> what if, after all the worrying
On 21 July 2015 at 00:34, Ben Finney wrote:
> Paul Moore writes:
>
>> Again, I'm sorry to pick on one sentence out of context, but it cut
>> straight to my biggest fear when doing a commit (on any project) -
>> what if, after all the worrying and consideration I put into doing
>> this commit, peo
On 20/07/2015 19:48, Christie Wilson wrote:
> I am terrified of replying to this thread since so many folks on it seem
> unhappy that it is continuing, but I want to +1 what Erik said.
Don't be terrified :)
But do understand that, in general, and especially for this
already-noisy thread, the righ
I am terrified of replying to this thread since so many folks on it seem
unhappy that it is continuing, but I want to +1 what Erik said.
Robert's solution is downright inspiring in how it gets to the heart of the
problem that the assret/assert feature is trying to address, and as a
frequent user o
On 21 July 2015 at 21:19, Paul Moore wrote:
> On 21 July 2015 at 11:03, Ben Finney wrote:
>> * If challenged to do so, could one (the contributor) present a
>> compelling justification for the change?
>>
>> This is what I claim Paul Moore's doubt (fear?) is indicative of. I
>> maintain that
On 21 July 2015 at 11:03, Ben Finney wrote:
> * If challenged to do so, could one (the contributor) present a
> compelling justification for the change?
>
> This is what I claim Paul Moore's doubt (fear?) is indicative of. I
> maintain that this doubt is quite healthy: it helps the contribut
Nick Coghlan writes:
> On 20 July 2015 at 22:34, Ben Finney wrote:
> > Paul Moore writes:
> >
> >> […] my biggest fear when doing a commit (on any project) - what if,
> >> after all the worrying and consideration I put into doing this
> >> commit, people disagree with me (or worse still, I made
Hello,
since this thread is restarting in debriefing mode: one thing struck me
as a non-committer following python-dev.
It seems that we (non-committers) have a difficulty making the
distinction between pre-implementation design discussions (PEPs beeing
the typical example), where relevant techni
On 20 July 2015 at 22:34, Ben Finney wrote:
> Paul Moore writes:
>
>> Again, I'm sorry to pick on one sentence out of context, but it cut
>> straight to my biggest fear when doing a commit (on any project) -
>> what if, after all the worrying and consideration I put into doing
>> this commit, peo
24 matches
Mail list logo
