Gavin D'souza added the comment:
@serhiy.storchaka That makes perfect sense. Could we do something to add a
parameter perhaps, to evaluate literal paths to not bread existing code?
although this isn't "needed" but it'd be neat
Gavin D'souza added the comment:
Thank you @xtreak, I'm aware of "os.path.expanduser" and have used it
extensively; I created this issue if we could do something about handling this
internally in zipfile too.
--
___
Py
New submission from Gavin D'souza :
I have a tool that works as a wrapper over a web framework which in turn
utilizes a virtualenv environment. So every app to be installed for a project
is installed in it's own env folder.
Recently, the virtualenv has been breakin
New submission from Gavin D'souza :
Related library: zipfile
Since zipfile allows relative dotted paths too, should shell-like paths,
specifically with ~ (tilde) be allowed too?
This feels like unexpected behaviour and confusing for users as method
"is_zipfile" returns Fal
Gavin D'souza added the comment:
if pprint is called without parameters, it returns a TypeError
>>> pprint()
Traceback (most recent call last):
File "", line 1, in
TypeError: pprint() missing 1 required positional argument: 'object'
it would be beneficial
New submission from Gavin D'souza :
For a simple string input, pprint would be expected to return an output similar
to print. However, the functionality differs
### Code:
import time
from pprint import pprint
start = time.time()
time.sleep(0.5)
object_made = time.time()
time.sleep(0.5)
