[issue35896] sysconfig.get_platform returns wrong value when Python 32b is running under Windows 64b

[jcrmatos]

jcrmatos  added the comment:

Then what is the difference between sysconfig.get_platform and sys.platform? 
When should we use one or the other?

Maybe changing sys.platform to 'win' instead of 'win32', like was done with 
'linux' in Python 3.3 (changed from 'linux2' and 'linux3') would be a step in 
standardization and simplification.

Another one is sys.platform and sysconfig.platform return 'win32' and os.name 
returns 'nt'. Can't it be changed (in Python 4) to 'win', maybe with a 
deprecation warning starting in 3.8?

--

___
Python tracker 
<https://bugs.python.org/issue35896>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35896] sysconfig.get_platform returns wrong value when Python 32b is running under Windows 64b

[jcrmatos]

jcrmatos  added the comment:

That's the name of the subsystem, not the platform.
Check the article you indicated
"In computing on Microsoft platforms, SysWoW64 (Windows 32-bit on Windows 
64-bit) is a subsystem..."

--

___
Python tracker 
<https://bugs.python.org/issue35896>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35896] sysconfig.get_platform returns wrong value when Python 32b is running under Windows 64b

[jcrmatos]

New submission from jcrmatos :

sysconfig.get_platform returns wrong value when Python 32b is running under 
Windows 64b.
It should return win-amd64 and returns win32.

--
messages: 334841
nosy: jcrmatos
priority: normal
severity: normal
status: open
title: sysconfig.get_platform returns wrong value when Python 32b is running 
under Windows 64b
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

___
Python tracker 
<https://bugs.python.org/issue35896>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35858] Consider adding the option of running shell/console commands inside the REPL

[jcrmatos]

jcrmatos  added the comment:

I will, thanks.

--
stage:  -> resolved
status: open -> closed

___
Python tracker 
<https://bugs.python.org/issue35858>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Thank you all for the help.

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35858] Consider adding the option of running shell/console commands inside the REPL

[jcrmatos]

jcrmatos  added the comment:

Yes, I understand that, but I don't see why that should prevent this feature 
from going forward.

--

___
Python tracker 
<https://bugs.python.org/issue35858>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35858] Consider adding the option of running shell/console commands inside the REPL

[jcrmatos]

New submission from jcrmatos :

Consider adding the option of running shell/console commands inside the REPL.
Something like
>>>!ls

--
messages: 334556
nosy: jcrmatos
priority: normal
severity: normal
status: open
title: Consider adding the option of running shell/console commands inside the 
REPL
type: enhancement
versions: Python 3.8

___
Python tracker 
<https://bugs.python.org/issue35858>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

I deleted the fork and started again.
This time I didn't PR to my own fork but to cpython master.
It is now waiting for review, "skip news" labeling and CLA (I'm still waiting 
on my request).

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

Change by jcrmatos :


--
keywords: +patch, patch, patch, patch
pull_requests: +11532, 11533, 11534, 11535
stage: needs patch -> patch review

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

Change by jcrmatos :


--
keywords: +patch, patch, patch
pull_requests: +11532, 11533, 11534
stage: needs patch -> patch review

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

Change by jcrmatos :


--
keywords: +patch
pull_requests: +11532
stage: needs patch -> patch review

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

Change by jcrmatos :


--
keywords: +patch, patch
pull_requests: +11532, 11533
stage: needs patch -> patch review

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

I didn't do anything locally. I did the change and preview it on GitHub's web 
interface.

Has I said, I did a PR to my own fork and now I think I have to do a PR to the 
cpython master. Is that correct?
The PR to my own fork was required, or the commit was enough?

Now I have an option to delete the fix-issue-35835 branch.
Should I do it? I read some Git tutorials and I think I can, but can you 
confirm?


Thanks in advance,

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

Yes, I signed the CLA and now I have to wait at least 1 business day.
So I will wait for that confirmation before making the PR to the CPython repo.

Thanks,

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

On the previous message I forgot to mention that the pull request was made in 
my fork, not the cpython repo.
Should I made a PR in the cpython repo at this point?

Thanks,

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

I'm using Github web interface.
I did these steps:
- Forked cpython and changed the pdb.rst file.
- Created a branch called "fix-issue-35835".
- Made the commit with description "Add reference to Python 3.7 new function 
breakpoint()".
- Made the pull request with title "bpo-35835: Add reference to Python 3.7 new 
function breakpoint()".
- Made the merge commit.

Now I have an option to delete the fix-issue-35835 branch.
Should I do it? I read some Git tutorials and I think I can, but can you 
confirm?

After that, how should I procede to create the patch?

Thanks,

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

Yes, I'm interested in learning, thanks.
I use Windows not Linux. Is that a problem?
I will read the guide and let you know if I have any questions. Thanks again.

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

I'm sorry, I have no idea how to do it.

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

In my first message I said exactly that (the replacement used the previous 
text, if you check it).

I'm ok with the wording from Cheryl. How about you Karthikeyan?

Thanks,

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

jcrmatos  added the comment:

Hello,

What about like this
import pdb; pdb.set_trace()
New in version 3.7: breakpoint() is preferable to using the previous line.

Thanks,

JM

--

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35836] ZeroDivisionError class should have a __name__ attr

[jcrmatos]

jcrmatos  added the comment:

Hello,

You are correct. My bad.

Thanks,

JM

--

___
Python tracker 
<https://bugs.python.org/issue35836>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35836] ZeroDivisionError class should have a __name__ attr

[jcrmatos]

New submission from jcrmatos :

Hello,

When trying this
try:
1/0
except Exception as exc:
print(type(exc))  # returns 
print(exc.__name__)  # returns AttributeError: 'ZeroDivisionError' object 
has no attribute '__name__'

I believe all classes should have a __name__ attr, correct?

It would be nice to check all the other exceptions to see if any other is also 
missing the __name__ attr.

Thanks,

JM

--
messages: 334416
nosy: jcrmatos
priority: normal
severity: normal
status: open
title: ZeroDivisionError class should have a __name__ attr
versions: Python 3.7

___
Python tracker 
<https://bugs.python.org/issue35836>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35835] There is no mention of breakpoint() in the pdb documentation

[jcrmatos]

New submission from jcrmatos :

In the Pdb documentation, found at
https://docs.python.org/3.7/library/pdb.html?highlight=pdb#module-pdb
there is no mention of breakpoint().

In my opinion, this text

import pdb; pdb.set_trace()

should be replaced with

import pdb; pdb.set_trace()
New in version 3.7: breakpoint() replaces the previous line.

Thanks,

JM

--
messages: 334406
nosy: jcrmatos
priority: normal
severity: normal
status: open
title: There is no mention of breakpoint() in the pdb documentation
type: enhancement
versions: Python 3.7, Python 3.8

___
Python tracker 
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31613] tkinter.simpledialog default buttons (not buttonbox) are not localized, unlike all messagebox

[jcrmatos]

jcrmatos  added the comment:

Hello,

I would expect the same behaviour as askopenfilename from tkinter.filedialog 
where the buttons are localized (in my case in Portuguese).

What I get is the buttons (in tkinter.simpledialog) are always in English.

Best regards,

JM

--

___
Python tracker 
<https://bugs.python.org/issue31613>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31422] tkinter.messagebox and tkinter.filedialog don't show default button's keyboard shortcuts

[jcrmatos]

jcrmatos  added the comment:

Hello,

There are no parameters for the buttons.

There is a difference in behaviour between messagebox windows (no shortcuts at 
all) to askopenfilename from tkinter.filedialog where the Open button has teh 
shortcut (but the Cancel one doesn't).


Best regards,

JM

--

___
Python tracker 
<https://bugs.python.org/issue31422>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31422] tkinter.messagebox and tkinter.filedialog don't show default button's keyboard shortcuts

[jcrmatos]

jcrmatos  added the comment:

Hello,

Here it is.


from tkinter import Tk
from tkinter.messagebox import askokcancel, showerror


master=Tk()
showerror('Error', 'Error message', parent=master)
a = askokcancel('Error', 'Error message', parent=master)
master.mainloop()


Best regards,

JM

--

___
Python tracker 
<https://bugs.python.org/issue31422>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31613] tkinter.simpledialog default buttons (not buttonbox) are not localized, unlike all messagebox

[jcrmatos]

jcrmatos  added the comment:

Hello,

Here is some example code:

from tkinter import Label, Tk
from tkinter.simpledialog import Dialog


class CalendarDialog(Dialog):
def __init__(self, parent, title='', year=0, month=0):
self.year = year  # type: int
self.month = month  # type: int

Dialog.__init__(self, parent, 'Select a date')

def body(self, parent):
Label(parent, text='A label').pack()


master = Tk()
result = CalendarDialog(master, year=2017, month=9).result
master.mainloop()


Best regards,

JM

--

___
Python tracker 
<https://bugs.python.org/issue31613>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31613] tkinter.simpledialog default buttons (not buttonbox) are not localized, unlike all messagebox

[jcrmatos]

New submission from jcrmatos :

Hello,

tkinter.simpledialog default buttons (not buttonbox) are not localized, unlike 
all messagebox.

Best regards,

JM

--
components: Tkinter
messages: 303162
nosy: jcrmatos
priority: normal
severity: normal
status: open
title: tkinter.simpledialog default buttons (not buttonbox) are not localized, 
unlike all messagebox
type: behavior
versions: Python 3.5

___
Python tracker 
<https://bugs.python.org/issue31613>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31422] tkinter.messagebox and tkinter.filedialog don't show default button's keyboard shortcuts

[jcrmatos]

Change by jcrmatos :


--
versions: +Python 3.5 -Python 3.7

___
Python tracker 
<https://bugs.python.org/issue31422>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31422] tkinter.messagebox and tkinter.filedialog don't show default button's keyboard shortcuts

[jcrmatos]

jcrmatos added the comment:

Hello,

I can't be more specific.

The problem is that the tkinter.messagebox windows (askokcancel, askyesno, 
showerror, showinfo, etc.) default buttons (Ok, Cancel, Yes, No, etc.) don't 
show the default keyboard shortcuts/accelerators.
I believe they should. Is it an incorrect assumpption?

Thanks,

JM

--

___
Python tracker 
<https://bugs.python.org/issue31422>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31422] tkinter.messagebox and tkinter.filedialog don't show default button's keyboard shortcuts

[jcrmatos]

New submission from jcrmatos:

tkinter.messagebox windows (eg. askokcancel, showerror, showinfo, ...) in 
Tkinter 8.6 running on Python 3.5.3, don't don't show the keyboard 
shortcuts/accelerators in the default buttons.

And the askopenfilename from tkinter.filedialog only shows the Open one. The 
Cancel does not appear and does not work.

I'm using it under Windows 7 Pro.

--
components: Tkinter
messages: 301893
nosy: jcrmatos
priority: normal
severity: normal
status: open
title: tkinter.messagebox and tkinter.filedialog don't show default button's 
keyboard shortcuts
type: behavior
versions: Python 3.5

___
Python tracker 
<https://bugs.python.org/issue31422>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28576] Uninstalling Py352 x86 with /uninstall option does not remove prepended paths

[jcrmatos]

jcrmatos added the comment:

Hello,

The GUI uninstall removes the prepended paths w/o requiring a reboot, so I see 
no reason why the /uninstall method shouldn't do it too.

I did try to reboot afterwards, but the paths remain.

I also tested on another PC, with Windows 8.1 x64, with the same results.

What is strange is that the /uninstall method removes the .PY and .PYW from the 
PATHEXT env var, but keeps the prepended paths.
I attached the logs as requested.

All tries were made using using

python-3.5.2.exe InstallAllUsers=1 CompileAll=1 InstallLauncherAllUsers=0 
PrependPath=1 /passive

for installation and

python-3.5.2.exe /uninstall

for uninstallation.

Best regards,

JM

--
Added file: http://bugs.python.org/file45304/Temp.zip

___
Python tracker 
<http://bugs.python.org/issue28576>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28576] Uninstalling Py352 x86 with /uninstall option does not remove prepended paths

[jcrmatos]

New submission from jcrmatos:

Hello,

When uninstalling Py352 x86 with the /uninstall option, it doesn't remove the 
prepended paths that were added on installation (unlike the GUI uninstall which 
removes them).

My system is a Win7ProSP1 x64.

Best regards,

JM

--
components: Installation, Windows
messages: 279852
nosy: jcrmatos, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Uninstalling Py352 x86 with /uninstall option does not remove prepended 
paths
type: behavior
versions: Python 3.5

___
Python tracker 
<http://bugs.python.org/issue28576>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28209] Exe or MSI unable to find Py3.5

[jcrmatos]

New submission from jcrmatos:

Exe or MSI created by
python setup.py bdist_wininst
and
python setup.py bdist_msi
on a Py3.5 are unable to find Py3.5 installed.
The build machine is not the same as the installation machine (destination).
Tried changing Py3.5 installation on the destination from user mode to all 
users, same result.

--
components: Distutils
messages: 276988
nosy: dstufft, eric.araujo, jcrmatos
priority: normal
severity: normal
status: open
title: Exe or MSI unable to find Py3.5
type: behavior
versions: Python 3.5

___
Python tracker 
<http://bugs.python.org/issue28209>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com