Hi

This is probably a dumb newbie question but I've just started to learn
python3 and eval() isn't behaving as I'd expect in that it works for
some things and not others. eg:

>>> eval("1+1")
2 >>> eval("print(123)")
123
>>> eval("for i in range(1,10): i")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<string>", line 1
for i in range(1,10): i
^
SyntaxError: invalid syntax

Why did the 3rd one fail? Does it not handle complex expressions?

Thanks for any help

Muttley@dastardlyhq.com writes:

> Hi

It looks like you posted this question via Usenet. comp.lang.python is
essentially dead as a Usenet group. It exists, and gets NNTP versions
of mail sent to the mailing list, but nothing posted to the group via
NNTP get send on the mailing list. I prefer Usenet and dislike mailing
lists but that just means I can't really contribute to this "group"

The "python-list" an an excellent resource (if you like the email
interface) and you can subscribe here:

https://mail.python.org/mailman/listinfo/python-list>,

> This is probably a dumb newbie question but I've just started to learn
> python3 and eval() isn't behaving as I'd expect in that it works for
> some things and not others. eg:
>
>>>> eval("1+1")
> 2
>>>> eval("print(123)")
> 123
>>>> eval("for i in range(1,10): i")
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "<string>", line 1
> for i in range(1,10): i
> ^
> SyntaxError: invalid syntax
>
> Why did the 3rd one fail? Does it not handle complex expressions?

It handles only expressions, and "for i in range(1,10): i" is not an
expression. You can use

>>> exec("for i in range(1,10): i")

or, to confirm that something is happening:

>>> exec("for i in range(1,10): print(i)")
1 2
3 4
5 6
7 8
9

See: https://docs.python.org/3/library/functions.html?highlight=eval#eval
and the immediately following entry.

--
Ben.

On Sat, 28 Jan 2023 at 11:45, <Muttley@dastardlyhq.com> wrote:
>
> Hi
>
> This is probably a dumb newbie question but I've just started to learn
> python3 and eval() isn't behaving as I'd expect in that it works for
> some things and not others. eg:
>
> >>> eval("1+1")
> 2
> >>> eval("print(123)")
> 123
> >>> eval("for i in range(1,10): i")
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "<string>", line 1
> for i in range(1,10): i
> ^
> SyntaxError: invalid syntax
>
> Why did the 3rd one fail? Does it not handle complex expressions?
>

There's a difference between *expressions* (which have values) and
*statements* (which do stuff, including control flow like loops). You
may want the exec function instead.

ChrisA

On 28/01/2023 05.37, Muttley@dastardlyhq.com wrote:
> This is probably a dumb newbie question but I've just started to learn
> python3 and eval() isn't behaving as I'd expect in that it works for
> some things and not others. eg:
>
>>>> eval("1+1")
> 2
>>>> eval("print(123)")
> 123
>>>> eval("for i in range(1,10): i")
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "<string>", line 1
> for i in range(1,10): i
> ^
> SyntaxError: invalid syntax
>
> Why did the 3rd one fail? Does it not handle complex expressions?

eval() is very powerful, and therefore rather dangerous in the risks it
presents.

Thus, seems a strange/advanced question for a "newbie" to be asking. YMMV!

Do you know about the Python REPL?

If you open python within a terminal, each of the three
expressions/compound-statements listed will work, as desired, without
eval().

dn $ ... python
Python 3.11.1 (main, Jan 6 2023, 00:00:00) [GCC 12.2.1 20221121 (Red
Hat 12.2.1-4)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 1+1
2 >>> print( 123 )
123
>>> for i in range( 1, 10 ): i
....
1 2
3 4
5 6
7 8
9 >>> exit()

--
Regards,
=dn

On Fri, 27 Jan 2023 21:04:58 +0000
Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>Muttley@dastardlyhq.com writes:
>
>> Hi
>
>It looks like you posted this question via Usenet. comp.lang.python is
>essentially dead as a Usenet group. It exists, and gets NNTP versions
>of mail sent to the mailing list, but nothing posted to the group via
>NNTP get send on the mailing list. I prefer Usenet and dislike mailing
>lists but that just means I can't really contribute to this "group"
>
>The "python-list" an an excellent resource (if you like the email
>interface) and you can subscribe here:
>
>https://mail.python.org/mailman/listinfo/python-list>,
>
>> This is probably a dumb newbie question but I've just started to learn
>> python3 and eval() isn't behaving as I'd expect in that it works for
>> some things and not others. eg:
>>
>>>>> eval("1+1")
>> 2
>>>>> eval("print(123)")
>> 123
>>>>> eval("for i in range(1,10): i")
>> Traceback (most recent call last):
>> File "<stdin>", line 1, in <module>
>> File "<string>", line 1
>> for i in range(1,10): i
>> ^
>> SyntaxError: invalid syntax
>>
>> Why did the 3rd one fail? Does it not handle complex expressions?
>
>It handles only expressions, and "for i in range(1,10): i" is not an
>expression. You can use
>
>>>> exec("for i in range(1,10): i")

Ok, thanks.

On Sat, 28 Jan 2023 14:22:01 +1300
dn <PythonList@DancesWithMice.info> wrote:
>On 28/01/2023 05.37, Muttley@dastardlyhq.com wrote:
>> This is probably a dumb newbie question but I've just started to learn
>> python3 and eval() isn't behaving as I'd expect in that it works for
>> some things and not others. eg:
>>
>>>>> eval("1+1")
>> 2
>>>>> eval("print(123)")
>> 123
>>>>> eval("for i in range(1,10): i")
>> Traceback (most recent call last):
>> File "<stdin>", line 1, in <module>
>> File "<string>", line 1
>> for i in range(1,10): i
>> ^
>> SyntaxError: invalid syntax
>>
>> Why did the 3rd one fail? Does it not handle complex expressions?
>
>eval() is very powerful, and therefore rather dangerous in the risks it
>presents.
>
>Thus, seems a strange/advanced question for a "newbie" to be asking. YMMV!

Well ok, new-ish :)

>Do you know about the Python REPL?

Haven't learnt the acronyms yet.

>If you open python within a terminal, each of the three
>expressions/compound-statements listed will work, as desired, without
>eval().

Umm, yeah, thats kind of obvious isn't it?

On 1/27/2023 9:37 AM, Muttley@dastardlyhq.com wrote:
> Hi
>
> This is probably a dumb newbie question but I've just started to learn
> python3 and eval() isn't behaving as I'd expect in that it works for
> some things and not others. eg:
>
>>>> eval("1+1")
> 2
>>>> eval("print(123)")
> 123
>>>> eval("for i in range(1,10): i")
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "<string>", line 1
> for i in range(1,10): i
> ^
> SyntaxError: invalid syntax
>
> Why did the 3rd one fail? Does it not handle complex expressions?
>
> Thanks for any help
>
>
>

This might -- or might not -- be useful:

eval( "print( [i for i in range(1, 10)] )" )

It prints a list, but you probably knew that:

[1, 2, 3, 4, 5, 6, 7, 8, 9]

Louis

On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
> Muttley@dastardlyhq.com writes:
>
> > Hi
>
> It looks like you posted this question via Usenet. comp.lang.python is
> essentially dead as a Usenet group. It exists, and gets NNTP versions
> of mail sent to the mailing list, but nothing posted to the group via
> NNTP get send on the mailing list.

This is wrong. I did get Muttley's any your postings via the
mailing-list.

(I also get Stefan Ram's postings despite his "no distribution outside
of Usenet" header).

hp

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

Muttley@dastardlyhq.com wrote:
> On Sat, 28 Jan 2023 14:22:01 +1300
> dn <PythonList@DancesWithMice.info> wrote:
>> Do you know about the Python REPL?
>
> Haven't learnt the acronyms yet.

REPL stands for "Read Evaluate Print Loop". It basically refers to the
interactive interpreter, which reads input you type, evaluates it,
prints the result, and loops (repeatedly does that).

An interesting point from your examples is that the output from the
first two comes from different steps in that loop.

>>> eval("1+1")
2

Here, the E (evaluation) step runs eval("1+1"), which returns 2. The P
(print) step then prints that result. If this was in a script, you
wouldn't see any output, and the statement is pretty much useless -
you'd need to assign the result to a variable or explicitly print it.

>>> eval("print(123)")
123

Here, the E step runs eval("print(123)"), which prints 123 and returns
None. The P step doesn't print anything if the result is None. You'd
still see that output if this was in a script.

Using eval in those examples is pretty pointless, since:
>>> 1+1
>>> print(123)
would produce the same results - but of course they were just simple
examples.

--
Mark.

On 2023-01-28, Peter J. Holzer <hjp-python@hjp.at> wrote:
> On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
>> It looks like you posted this question via Usenet. comp.lang.python is
>> essentially dead as a Usenet group. It exists, and gets NNTP versions
>> of mail sent to the mailing list, but nothing posted to the group via
>> NNTP get send on the mailing list.
>
> This is wrong. I did get Muttley's any your postings via the
> mailing-list.

Yes, it's certainly false. I only ever post via the newsgroup,
and I can see my postings reach the list because they appear
in the list archive on the web.

https://mail.python.org/pipermail/python-list/

Jon Ribbens <jon+usenet@unequivocal.eu> wrote:
> On 2023-01-28, Peter J. Holzer <hjp-python@hjp.at> wrote:
> > On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
> >> It looks like you posted this question via Usenet. comp.lang.python is
> >> essentially dead as a Usenet group. It exists, and gets NNTP versions
> >> of mail sent to the mailing list, but nothing posted to the group via
> >> NNTP get send on the mailing list.
> >
> > This is wrong. I did get Muttley's any your postings via the
> > mailing-list.
>
> Yes, it's certainly false. I only ever post via the newsgroup,
> and I can see my postings reach the list because they appear
> in the list archive on the web.
>
As far as I am aware the mirroring of the Python mailing list on
comp.lan.python works perfectly. I love gmane! :-)

--
Chris Green
·

Chris Green <cl@isbd.net> wrote:
> Jon Ribbens <jon+usenet@unequivocal.eu> wrote:
> > On 2023-01-28, Peter J. Holzer <hjp-python@hjp.at> wrote:
> > > On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
> > >> It looks like you posted this question via Usenet. comp.lang.python is
> > >> essentially dead as a Usenet group. It exists, and gets NNTP versions
> > >> of mail sent to the mailing list, but nothing posted to the group via
> > >> NNTP get send on the mailing list.
> > >
> > > This is wrong. I did get Muttley's any your postings via the
> > > mailing-list.
> >
> > Yes, it's certainly false. I only ever post via the newsgroup,
> > and I can see my postings reach the list because they appear
> > in the list archive on the web.
> >
> As far as I am aware the mirroring of the Python mailing list on
> comp.lan.python works perfectly. I love gmane! :-)
>
That is, of course, comp.lang.python. Too much wine! :-)

--
Chris Green
·

On Sat, 28 Jan 2023 15:30:59 +0100, "Peter J. Holzer" <hjp-python@hjp.at>
declaimed the following:

>On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
>> Muttley@dastardlyhq.com writes:
>>
>> > Hi
>>
>> It looks like you posted this question via Usenet. comp.lang.python is
>> essentially dead as a Usenet group. It exists, and gets NNTP versions
>> of mail sent to the mailing list, but nothing posted to the group via
>> NNTP get send on the mailing list.
>
>This is wrong. I did get Muttley's any your postings via the
>mailing-list.
>

I had been tempted to ask when the list<>newsgroup link had changed,
since it hadn't been announced...

Now -- last time I checked the gmane server says posting is prohibited.
I used to use gmane as it retrieved directly from the mailing list (which
has been filtered from much spam) and not Usenet (and its open spam
problem).

--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

On Sat, 28 Jan 2023 20:07:44 +0000, Chris Green <cl@isbd.net> declaimed the
following:

>As far as I am aware the mirroring of the Python mailing list on
>comp.lan.python works perfectly. I love gmane! :-)

Is gmane's gmane.comp.python.general allowing posts to go through
again? I had to revert to comp.lang.python some time back when gmane kept
rejecting outgoing posts.

--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

On Sun, 29 Jan 2023 at 12:07, Chris Green <cl@isbd.net> wrote:
>
> Chris Green <cl@isbd.net> wrote:
> > Jon Ribbens <jon+usenet@unequivocal.eu> wrote:
> > > On 2023-01-28, Peter J. Holzer <hjp-python@hjp.at> wrote:
> > > > On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
> > > >> It looks like you posted this question via Usenet. comp.lang.python is
> > > >> essentially dead as a Usenet group. It exists, and gets NNTP versions
> > > >> of mail sent to the mailing list, but nothing posted to the group via
> > > >> NNTP get send on the mailing list.
> > > >
> > > > This is wrong. I did get Muttley's any your postings via the
> > > > mailing-list.
> > >
> > > Yes, it's certainly false. I only ever post via the newsgroup,
> > > and I can see my postings reach the list because they appear
> > > in the list archive on the web.
> > >
> > As far as I am aware the mirroring of the Python mailing list on
> > comp.lan.python works perfectly. I love gmane! :-)
> >
> That is, of course, comp.lang.python. Too much wine! :-)
>

You can run Python with wine, but it runs natively and that's usually better :)

ChrisA

"Peter J. Holzer" <hjp-python@hjp.at> writes:

> On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
>> Muttley@dastardlyhq.com writes:
>>
>> > Hi
>>
>> It looks like you posted this question via Usenet. comp.lang.python is
>> essentially dead as a Usenet group. It exists, and gets NNTP versions
>> of mail sent to the mailing list, but nothing posted to the group via
>> NNTP get send on the mailing list.
>
> This is wrong. I did get Muttley's any your postings via the
> mailing-list.

Ah, OK. I thought that was the case but I am obviously wrong. Has
there been a change, or have I been wrong for a long time!?

There may be a timing issue because I tried to find a reply a Usenet
injected post from a mailing-list user and, at the time I looked, I
could not find one.

--
Ben.

On 2023-01-29, Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
> "Peter J. Holzer" <hjp-python@hjp.at> writes:
>
>> On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
>>> Muttley@dastardlyhq.com writes:
>>>
>>> > Hi
>>>
>>> It looks like you posted this question via Usenet. comp.lang.python is
>>> essentially dead as a Usenet group. It exists, and gets NNTP versions
>>> of mail sent to the mailing list, but nothing posted to the group via
>>> NNTP get send on the mailing list.
>>
>> This is wrong. I did get Muttley's any your postings via the
>> mailing-list.
>
> Ah, OK. I thought that was the case but I am obviously wrong. Has
> there been a change, or have I been wrong for a long time!?

I'm not aware of any significant period in the last twenty-one years
that it hasn't been working. Although sometimes it does feel like it
isn't, in that I reply to a post with an answer and then several
other people reply significantly later with the same answer, as if
my one had never existed... but whenever I check into it, my message
has actually always made it to the list.

Jon Ribbens <jon+usenet@unequivocal.eu> writes:

> On 2023-01-29, Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>> "Peter J. Holzer" <hjp-python@hjp.at> writes:
>>
>>> On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
>>>> Muttley@dastardlyhq.com writes:
>>>>
>>>> > Hi
>>>>
>>>> It looks like you posted this question via Usenet. comp.lang.python is
>>>> essentially dead as a Usenet group. It exists, and gets NNTP versions
>>>> of mail sent to the mailing list, but nothing posted to the group via
>>>> NNTP get send on the mailing list.
>>>
>>> This is wrong. I did get Muttley's any your postings via the
>>> mailing-list.
>>
>> Ah, OK. I thought that was the case but I am obviously wrong. Has
>> there been a change, or have I been wrong for a long time!?
>
> I'm not aware of any significant period in the last twenty-one years
> that it hasn't been working. Although sometimes it does feel like it
> isn't, in that I reply to a post with an answer and then several
> other people reply significantly later with the same answer, as if
> my one had never existed... but whenever I check into it, my message
> has actually always made it to the list.

I have had the same experience and, as a result, I rarely post. Maybe
what I have to say is simply not interesting!

--
Ben.

On Saturday, January 28, 2023 at 10:02:57 PM UTC-5, Ben Bacarisse wrote:
> Jon Ribbens <jon+u...@unequivocal.eu> writes:
>
> > On 2023-01-29, Ben Bacarisse <ben.u...@bsb.me.uk> wrote:
> >> "Peter J. Holzer" <hjp-p...@hjp.at> writes:
> >>
> >>> On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
> >>>> Mut...@dastardlyhq.com writes:
> >>>>
> >>>> > Hi
> >>>>
> >>>> It looks like you posted this question via Usenet. comp.lang.python is
> >>>> essentially dead as a Usenet group. It exists, and gets NNTP versions
> >>>> of mail sent to the mailing list, but nothing posted to the group via
> >>>> NNTP get send on the mailing list.
> >>>
> >>> This is wrong. I did get Muttley's any your postings via the
> >>> mailing-list.
> >>
> >> Ah, OK. I thought that was the case but I am obviously wrong. Has
> >> there been a change, or have I been wrong for a long time!?
> >
> > I'm not aware of any significant period in the last twenty-one years
> > that it hasn't been working. Although sometimes it does feel like it
> > isn't, in that I reply to a post with an answer and then several
> > other people reply significantly later with the same answer, as if
> > my one had never existed... but whenever I check into it, my message
> > has actually always made it to the list.
> I have had the same experience and, as a result, I rarely post. Maybe
> what I have to say is simply not interesting!
>
> --
> Ben.

If I remember correctly, multiple regulars that use the mailing list
mentioned that they "killfiled" posts originating from Google groups.
This may contribute to such situations.

Igor Berger <codewizard@gmail.com> writes:

> On Saturday, January 28, 2023 at 10:02:57 PM UTC-5, Ben Bacarisse wrote:
>> Jon Ribbens <jon+u...@unequivocal.eu> writes:
>>
>> > On 2023-01-29, Ben Bacarisse <ben.u...@bsb.me.uk> wrote:
>> >> "Peter J. Holzer" <hjp-p...@hjp.at> writes:
>> >>
>> >>> On 2023-01-27 21:04:58 +0000, Ben Bacarisse wrote:
>> >>>> Mut...@dastardlyhq.com writes:
>> >>>>
>> >>>> > Hi
>> >>>>
>> >>>> It looks like you posted this question via Usenet. comp.lang.python is
>> >>>> essentially dead as a Usenet group. It exists, and gets NNTP versions
>> >>>> of mail sent to the mailing list, but nothing posted to the group via
>> >>>> NNTP get send on the mailing list.
>> >>>
>> >>> This is wrong. I did get Muttley's any your postings via the
>> >>> mailing-list.
>> >>
>> >> Ah, OK. I thought that was the case but I am obviously wrong. Has
>> >> there been a change, or have I been wrong for a long time!?
>> >
>> > I'm not aware of any significant period in the last twenty-one years
>> > that it hasn't been working. Although sometimes it does feel like it
>> > isn't, in that I reply to a post with an answer and then several
>> > other people reply significantly later with the same answer, as if
>> > my one had never existed... but whenever I check into it, my message
>> > has actually always made it to the list.
>>
>> I have had the same experience and, as a result, I rarely post. Maybe
>> what I have to say is simply not interesting!
>>
>
> If I remember correctly, multiple regulars that use the mailing list
> mentioned that they "killfiled" posts originating from Google groups.
> This may contribute to such situations.

Ah, that may explain most of my confusion. I know I stopped posting
because there didn't seem to be much engagement, but maybe it was just
many list members choosing not to see my posts rather than all list
members not being able to see my posts.

As I said, I did check to see if I could find a reply to a
Usenet-originated post from a list member but my not being able to find
one could just be down to many list members filtering Usenet posts.
It's clearly not universal.

--
Ben.

On 2023-01-29 02:09:28 -0000, Jon Ribbens via Python-list wrote:
> I'm not aware of any significant period in the last twenty-one years
> that
[the gateway]
> hasn't been working. Although sometimes it does feel like it isn't, in
> that I reply to a post with an answer and then several other people
> reply significantly later with the same answer, as if my one had never
> existed...

That's just because people don't read before they post.

Happens in any usenet group or mailing list (and probably in web forums,
too; but I don't really use those). I have to admit that I'm sometimes
guilty of this behaviour, too.

hp

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

On 2023-01-29, Peter J. Holzer <hjp-python@hjp.at> wrote:
> On 2023-01-29 02:09:28 -0000, Jon Ribbens via Python-list wrote:
>> I'm not aware of any significant period in the last twenty-one years
>> that
> [the gateway]
>> hasn't been working. Although sometimes it does feel like it isn't, in
>> that I reply to a post with an answer and then several other people
>> reply significantly later with the same answer, as if my one had never
>> existed...
>
> That's just because people don't read before they post.
>
> Happens in any usenet group or mailing list (and probably in web forums,
> too; but I don't really use those). I have to admit that I'm sometimes
> guilty of this behaviour, too.

Well, let's just assume for a moment that I'm familiar with Usenet and
with mailing lists ;-) This sort of replying-without-reading seems to
happen on comp.lang.python/python-list more than usual.

On 2023-01-28, Louis Krupp <lkrupp@invalid.pssw.com.invalid> wrote:
> On 1/27/2023 9:37 AM, Muttley@dastardlyhq.com wrote:

>>>>> eval("print(123)")
>> 123

Does OP expect the text to come from the eval or from the print?

>>> x = print( [i for i in range(1, 10)] )
[1, 2, 3, 4, 5, 6, 7, 8, 9]

>>> x
(nothing printed)

On 1/29/2023 4:15 PM, elvis-85792@notatla.org.uk wrote:
> On 2023-01-28, Louis Krupp <lkrupp@invalid.pssw.com.invalid> wrote:
>> On 1/27/2023 9:37 AM, Muttley@dastardlyhq.com wrote:
>
>
>>>>>> eval("print(123)")
>>> 123
>
>
> Does OP expect the text to come from the eval or from the print?
>
>>>> x = print( [i for i in range(1, 10)] )
> [1, 2, 3, 4, 5, 6, 7, 8, 9]
>
>>>> x
> (nothing printed)

Because print() returns nothing (i.e., the statement x is None is True).
Other common constructs that return nothing are append(), sort(), and
add(). It can be easy to forget this and write

l2 = l1.sort() # l2 == None

OTOH, you can (by slightly abusing the lambda) use this behavior to make
a lambda expression print what it's receiving:

>>> y = lambda x: print(f'Got {x}') or x**2
>>> z = y(3)
Got 3
>>> z
9 >>>

On Sun, 29 Jan 2023 23:57:51 -0500
Thomas Passin <list1@tompassin.net> wrote:
>On 1/29/2023 4:15 PM, elvis-85792@notatla.org.uk wrote:
>> On 2023-01-28, Louis Krupp <lkrupp@invalid.pssw.com.invalid> wrote:
>>> On 1/27/2023 9:37 AM, Muttley@dastardlyhq.com wrote:
>>
>>
>>>>>>> eval("print(123)")
>>>> 123
>>
>>
>> Does OP expect the text to come from the eval or from the print?
>>
>>>>> x = print( [i for i in range(1, 10)] )
>> [1, 2, 3, 4, 5, 6, 7, 8, 9]
>>
>>>>> x
>> (nothing printed)
>
>Because print() returns nothing (i.e., the statement x is None is True).

I don't understand this. What was the point of the upheaval of converting
the print command in python 2 into a function in python 3 if as a function
print() doesn't return anything useful? Surely even the length of the
formatted string as per C's sprintf() function would be helpful?