On 1/17/2023 8:46 PM, rbowman wrote:
On Tue, 17 Jan 2023 12:47:29 +, Stephen Tucker wrote:
2. Does the IDLE in Python 3.x behave the same way?
fwiw
Python 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license()" for more information.
s
On Tue, 17 Jan 2023 12:47:29 +, Stephen Tucker wrote:
> 2. Does the IDLE in Python 3.x behave the same way?
fwiw
Python 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license()" for more information.
str = ""
for c in range(157, 169):
s
Thanks a lot, Edmondo. Or better... Grazie mille.
On 1/17/2023 5:42 AM, Edmondo Giovannozzi wrote:
Sorry,
I was just creating an array of 400x10 elements that I fill with random
numbers:
a = np.random.randn(400,100_000)
Then I pick one element randomly, it is just a stupid sort on a
Il giorno martedì 17 gennaio 2023 alle 00:18:04 UTC+1 Dino ha scritto:
> On 1/16/2023 1:18 PM, Edmondo Giovannozzi wrote:
> >
> > As a comparison with numpy. Given the following lines:
> >
> > import numpy as np
> > a = np.random.randn(400,100_000)
> > ia = np.argsort(a[0,:])
> > a_elem = a[
I have four questions.
1. Can anybody explain the behaviour in IDLE (Python version 2.7.10)
reported below? (It seems that the way it renders a given sequence of bytes
depends on the sequence.)
2. Does the IDLE in Python 3.x behave the same way?
3. If it does, is this as it should behave?
4. If
