[issue36812] posix_spawnp returns error when used with file_actions

2019-05-06 Thread Matthew Tanous
New submission from Matthew Tanous : Ran into this on macOS while trying to play around with the new posix_spawn bindings. It appears to me that the file_actions path is not what is being used by file_actions here. It may be that I am misunderstanding something, but I thought I would bring

[issue36814] posix_spawn explicit file_actions=None throws error

2019-05-06 Thread Matthew Tanous
New submission from Matthew Tanous : Allowing posix_spawn file_actions to default to None works, but explicitly setting it throws a TypeError: Python 3.8.0a3 (v3.8.0a3:9a448855b5, Mar 25 2019, 17:05:20) [Clang 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", &

[issue36812] posix_spawnp returns error when used with file_actions

2019-05-06 Thread Matthew Tanous
Matthew Tanous added the comment: I have some updated information. This works as expected when I set the permissions properly using an octal number 0o777. The issue appears to be that when the permissions don't exist as specified, the PermissionError reports the process name, not the

[issue36812] posix_spawnp returns error when used with file_actions

2019-05-07 Thread Matthew Tanous
Matthew Tanous added the comment: Your example is an attempt to use Popen to run a file you don't have execute permissions for. In my example, it is not `whoami` that it is failing to create/open, but '.tmp/temp_file'. I would expect a `PermissionError: [Errno 13] Permission

[issue27135] nested list produced with multiplication is linked to the same list

2016-05-27 Thread Matthew Tanous
Matthew Tanous added the comment: It makes sense, except for this case is not true when "x" is an immutable data type - it appears as though something like [5] * n creates a list of totally separate elements (even if they start as the same thing). It is difficult to see a case whe

[issue27135] nested list produced with multiplication is linked to the same list

2016-05-26 Thread Matthew Tanous
New submission from Matthew Tanous: If I produce a list in this fashion: l = [[x] * n] * n I would expect that I would obtain a matrix-like structure. Instead, I get a list of the *same* list, such that the statement: l[x][y] = z would change, in essence, every value in "column"

[issue27135] nested list produced with multiplication is linked to the same list

2016-05-26 Thread Matthew Tanous
Matthew Tanous added the comment: I'm aware that it's how Python works at present. My point was that this is awkward and counter-intuitive, with no purpose I can see worth serving. "That's just how it works" seems to me a rather insufficient answer, especially for