!-Original Message-
!From: Tutor [mailto:tutor-bounces+crk=godblessthe...@python.org] On
!Behalf Of Dave Angel
!Sent: Tuesday, October 28, 2014 6:34 PM
!To: tutor@python.org
!Subject: Re: [Tutor] Would somebody kindly...
!
!
!>
! Explain this double speak(>:
!> [pair for pair in values i
!-Original Message-
!From: Cameron Simpson [mailto:c...@zip.com.au]
!Sent: Tuesday, October 28, 2014 6:31 PM
!To: Clayton Kirkwood
!Cc: 'Danny Yoo'; 'Python Tutor Mailing List'
!Subject: Re: [Tutor] Would somebody kindly...
!
!On 28Oct2014 18:02, Clayton Kirkwood wrote:
!>!> Explain this
On 28Oct2014 18:02, Clayton Kirkwood wrote:
!> Explain this double speak(>:
!>
Ah, Alan sent an answer also, but this one answers the last tidbit. Alan had
the some_list and pair the same name, presumably creating a temporary tuple and
when the loop is done, the temporary replaces the original
>
Explain this double speak(>:
> [pair for pair in values if key == pair[0]]
> I understand the ‘for pair in values’. I assume the first
> ‘pair’ creates the namespace
The namespace question depends on the version of Python. Python
2.x does not do any scoping.
But in version 3.x, the var
On 29/10/14 01:02, Clayton Kirkwood wrote:
Ah, Alan sent an answer also, but this one answers the last tidbit.
Alan had the some_list and pair the same name, presumably creating
> a temporary tuple and when the loop is done, the temporary
replaces the original.
Nope. If you re-read my post yo
Ah, Alan sent an answer also, but this one answers the last tidbit. Alan had
the some_list and pair the same name, presumably creating a temporary tuple and
when the loop is done, the temporary replaces the original.
Thanks
Clayton
!-Original Message-
!From: Danny Yoo [mailto:d...@has
On 28/10/14 23:13, Clayton Kirkwood wrote:
line either a tuple or list. The comprehension seems to act as a
subroutine or macro
In a sense yes, that's true.
You can find another explanation of list comprehensions and other
related functions in my tutorial (see .sig) in the Functional
Progra
On 28/10/14 23:13, Clayton Kirkwood wrote:
Explain this double speak(>:
[pair for pair in values if key == pair[0]]
A list comprehension is a specific form of a more general
construction called a generator expression. Its specific
in that it creates a list, hence the [] around it.
The general
On Tue, Oct 28, 2014 at 4:13 PM, Clayton Kirkwood wrote:
> Explain this double speak(>:
>
> [pair for pair in values if key == pair[0]]
Hi Clayton,
Here is a rewording of that expression to an approximately equivalent statement:
###
some_list = []
for pair in values:
if
Explain this double speak(>:
[pair for pair in values if key == pair[0]]
I understand the 'for pair in values'. I assume the first 'pair' creates the
namespace (although I am not sure how Python knows it's a tuple yet). I
think the outer [] make the line a comprehension ( If so, I don't seem t
On 10/28/2014 04:27 PM, Todd wrote:
> Centos has SELinux enabled by default. I dont know if SELinux is
> causing your problem, but it is always worth looking at.
>
> SELinux can keep a process from accessing files or executing another
> process.
>
> Try temporarily disabling SELinux by runnin
Centos has SELinux enabled by default. I dont know if SELinux is causing
your problem, but it is always worth looking at.
SELinux can keep a process from accessing files or executing another
process.
Try temporarily disabling SELinux by running setenforce=0 as root. Then
see if python does wha
On 28/10/14 19:23, Adam Jensen wrote:
platform. This is what I've discovered so far:
| | CentOS-6.5 | OpenBSD-5.5 | DragonFly-3.8.2 |
| bufsize | Python-3.4.1 | Python-3.3.2 | Python-3.3.3|
|-+--+--+-
On 10/28/2014 02:32 PM, Alan Gauld wrote:
> I tried -1 and 1 on my Lubuntu and it still works fine.
> Definitely weird, it begins to look like a CentOS build issue
> but what is CentOS doing different to Lubuntu/Suse/OpenBSD etc?
>
> From memory CentOS is basically a free version of Red Hat
> Ent
On 28/10/14 15:31, Adam Jensen wrote:
-
bufsize will be supplied as the corresponding argument to the open()
function when creating the stdin/stdout/stderr pipe file objects:
And I get these results (on CentOS-6.5-x86):
Update:
On 10/27/2014 09:50 PM, Adam Jensen wrote:
> What's weird is that I have two different python3.4 installations on
> this CentOS-6.5 machine and both have the same behavior (script hangs
> until Ctrl+C).
>
> I built this one (/opt/bin/python3.4) from source:
...
> But this one (~/anaconda3
16 matches
Mail list logo
