Nikhil Benesch added the comment:
So it looks like /usr/bin/python3 is just a shim that immediately execs the
real Python binary:
/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/bin/python3
This binary is identical to the one that ends up in
Nikhil Benesch added the comment:
Oops, sorry, I forgot to actually include the correct command in the
workaround. Here it is:
$ /usr/bin/python3 -c 'import venv; venv.create("venv2", symlinks=True);'
--
___
Py
Nikhil Benesch added the comment:
This issue continues to exist with the system Python on macOS. Here is how to
reproduce on macOS Catalina 10.15.7 and Xcode 12.1.
$ /usr/bin/python3 --version
Python 3.8.2
$ /usr/bin/python3 -c 'import venv; venv.create("venv");'
$ v
Nikhil Patel added the comment:
PR to add documentation still up-to-date and all checks successful just pending
review
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
___
Python tracker
<https://bugs.pyth
Nikhil Hegde added the comment:
Any ETA I can get on this?
--
___
Python tracker
<https://bugs.python.org/issue32152>
___
___
Python-bugs-list mailing list
Unsub
Nikhil Hegde added the comment:
This is also necessary in a case where two tests (say, a and b) are running in
parallel. Both tests access the same fileX.py
The coverage for fileX.py will not be accurate to reflect the usage by
tests a and b
--
versions: +Python 3.5, Python 3.6
Nikhil Hegde added the comment:
In the trace_generic.py file that I've attached, the changes are on line 331
--
Added file: https://bugs.python.org/file47300/trace_generic.py
___
Python tracker
<https://bugs.python.org/is
New submission from Nikhil Hegde :
Adding pid to filenames will avoid file write error when multiple processes
(specifically, multiple tests) are writing to the same .cover file
--
components: Library (Lib)
messages: 307110
nosy: nikhilh
priority: normal
severity: normal
status: open
New submission from Nikhil :
What I did
1) root file declared where operation will start and import hashlib for
getting hash signatures
2) os.walk for recursively diving into directory tree
3) open file and find sha256 digest and print it
4) close the file
5) recursively repeat all above 2 steps
New submission from Nikhil :
I have included the screen shot
--
files: Screenshot_20171011_222848.png
messages: 304164
nosy: Nik101
priority: normal
severity: normal
status: open
title: Issue in login
Added file: https://bugs.python.org/file47213/Screenshot_20171011_222848.png
Nikhil Patel added the comment:
I'd like to respectfully disagree with the suggestions/conclusions mentioned
here. I'll explain my reasoning and conclusions below.
First the short version - I'm fairly confident the leak actually has to do
with:
https://github.com/python/cpyt
Nikhil Patel added the comment:
I've written rst files containing documentation for the tkinter modules and
submitted a PR. Attempted to mimic the wording as well as style of existing
documentation to keep it consistent.
--
nosy: +npatel
___
P
Changes by Nikhil Patel :
--
pull_requests: +1953
___
Python tracker
<http://bugs.python.org/issue25237>
___
___
Python-bugs-list mailing list
Unsubscribe:
Nikhil Benesch added the comment:
Since it looks like development on this has stalled, I took the liberty of
compiling all prior patches
https://github.com/benesch/python-dtrace-tracker
and am actively working on merging them into one superpatch. I am neither a
Python nor a DTrace expert
Changes by Nikhil Benesch :
--
nosy: +benesch
___
Python tracker
<http://bugs.python.org/issue13405>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Nikhil Benesch :
--
nosy: +benesch
___
Python tracker
<http://bugs.python.org/issue14776>
___
___
Python-bugs-list mailing list
Unsubscribe:
16 matches
Mail list logo