Change by E. Paine :
--
components: -Distutils
resolution: out of date ->
status: closed -> open
___
Python tracker
<https://bugs.python.org/i
E. Paine added the comment:
I cannot reproduce. Taking a rectangle as an example,
canvas.bbox(canvas.create_rectangle(5, 5, 100, 100, width=1))
returns `(4, 4, 101, 101)` (rather than `(5, 5, 100, 100)`) because of rounding
while calculating the outline.
As a result, running
E. Paine added the comment:
I suspect this is just a MacOS behaviour, if not then it is a Tk bug. If you
really need to enforce the width, you could tell it to expand horizontally in
the layout. An example of this would be as follows:
tk.Frame(root, height=1, width=300).pack()
tk.OptionMenu
E. Paine added the comment:
This is a Tk/Windows issue, not tkinter. I tested the following on Windows 10
using Tk 8.6.9:
# Our entry
pack [entry .e]
# Causes the entry to fail
#tk_messageBox -title Title -message Message
#after 0 tk_messageBox -title Title -message Message
# Does
E. Paine added the comment:
This does not appear to be a problem anymore on Tk 8.6.11 so I think this issue
can be closed.
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
E. Paine added the comment:
I have also done a grep and believe the other affected parts from the user's
perspective are the debugger (I haven't checked if Mark's version also
suffers), the help dialog and hover tip (e.g. over the squeezer button).
> Would it work to just remove th
Change by E. Paine :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue42637>
___
___
New submission from E. Paine :
Currently IDLE, in some places, uses predefined colours which assume it is in
light mode. However, on the new Universal2 installers (I tested using 3.10.0a4)
this causes issues, where this can no longer be assumed.
Taking the "About IDLE" dialogue as
E. Paine added the comment:
Note: Tcl/Tk 8.6.11 was released a few days ago (thanks Kevin/Marc!).
--
___
Python tracker
<https://bugs.python.org/issue42
E. Paine added the comment:
> shouldn't the docs be made available for the currently maintained version of
> python?
Problem is the Tk version (which underpins tkinter) varies by distribution.
Currently, Windows and MacOS Intel installers are packaged with 8.6.8, while
MacOS Univ
E. Paine added the comment:
See also issue41851. I personally think that being able to compare whether two
tkinter variables point to the same Tk variable is very useful so needs to stay
in some form. However, I don't see any situation where comparing to see if two
tkinter variables
E. Paine added the comment:
> In my view, we should always create a default root if it's needed
I somewhat disagree. I think Serhiy has done a very good job (in what I've
reviewed so far) of balancing when a new root should or shouldn't be created
(e.g. does it make sense to create a
E. Paine added the comment:
> Are you gonna submit a PR
I think I assumed you would incorporate it into your PR unless you would prefer
it to be separate?
--
___
Python tracker
<https://bugs.python.org/issu
E. Paine added the comment:
Thank you for reporting this. I just have a few questions:
1. Which Python version are you using?
2. If Python 3.9.1, which installer did you use?
3. What does `tkinter.test.support.get_tk_patchlevel()` output?
4. Does your pygame example suffer the same issue (I
E. Paine added the comment:
Attached is a diff which moves the logic for `setup_master` to the tkinter
module while allowing it to still be imported from the tkinter.ttk module (in
case someone uses it...) The diff also replaces the logic in a few other places
to:
A. make behaviour more
Change by E. Paine :
--
title: Python release note tkinter problems -> Python macos11.0 release note
tkinter problems in news
___
Python tracker
<https://bugs.python.org/issu
New submission from E. Paine :
Under the "Installer news" for the Python 3.9.1 release, it notes:
"As we are waiting for an updated version of pip, please consider the macos11.0
installer experimental."
Is it worth also noting that tkinter has serious known problems that
E. Paine added the comment:
+1 I agree the current AttributeError is not suitable.
I would just copy the code from Lib/tkinter/__init__.py:2524 (or even better:
refactor it into its own method to avoid duplication). The code there, though,
would raise a similar AttributeError if the default
E. Paine added the comment:
While Tkinter could do it, I see no point in doing so. One thing that may be
worth looking into is only allowing IDLE to use fixed-width fonts, but maybe
this is just another of my crazy ideas... I think this can be safely closed
unless someone wants to make
E. Paine added the comment:
@Fredrik, can you comment on when we might expect effbot.org to become
available again? (i.e. is it worth us updating the docs to note that its down /
changing the link to the Wayback Machine?)
--
nosy: +effbot
Change by E. Paine :
--
components: +Build
nosy: +epaine, serhiy.storchaka
type: compile error -> enhancement
versions: -Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issu
E. Paine added the comment:
See issue34154. I'm personally against such changes because we don't know what
Tk version to write them for. Our documentation could be both outdated and too
recent, including kwargs not available to some people (because they are running
an older version
E. Paine added the comment:
Removed Alex from nosy because the link was an advertisement for an essay
writer.
--
nosy: -alexwriter2003
___
Python tracker
<https://bugs.python.org/issue40
E. Paine added the comment:
> we should at least opt out of dark mode for IDLE
That still leaves tkinter almost unusable when dark mode is turned on. I am
looking into solutions but am not hopeful (maybe we should ask Marc?).
@Ned, what are the alternatives if we decide 8.6.10 is not the
E. Paine added the comment:
It seems to be some weird internal mismatch. Code modified from
https://wiki.tcl-lang.org/page/Tk+differences+on+Mac+OS+X (see following)
suggests that dark mode is not enabled for the window (and yet we are getting
white foreground colours)
import tkinter as tk
E. Paine added the comment:
I just compiled Tk 8.6.10 and it has the same problems. So the question now is
whether we work-around it in Tkinter/IDLE or close this issue as third party.
--
___
Python tracker
<https://bugs.python.org/issue42
E. Paine added the comment:
Sorry, that was an important piece of information. It is worth noting that Text
widgets correctly change background to black.
--
___
Python tracker
<https://bugs.python.org/issue42
E. Paine added the comment:
> Are you running in dark mode?
Yes. It works fine in light mode.
--
___
Python tracker
<https://bugs.python.org/issu
Change by E. Paine :
Added file:
https://bugs.python.org/file49646/Screenshot-2020-12-02-at-12-46-06.png
___
Python tracker
<https://bugs.python.org/issue42541>
___
___
New submission from E. Paine :
When using tkinter from the universal2 package, the colours are completely
confused. Most text tries to white, even though the background is light and
this makes text in Entries completely unreadable (where the background is
white). This affects both Tk and Ttk
New submission from E. Paine :
Simple enough: we should make it very clear in the Devguide that creating a PR
from python:master to :master is not a good way to update your fork.
For context, I recently saw that a commit on a fork was showing as a mention on
a lot of the more recent commits
Change by E. Paine :
--
nosy: +davin, pitrou
versions: -Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue42406>
___
___
Python-bugs-list m
Change by E. Paine :
--
components: +Library (Lib)
type: -> behavior
versions: +Python 3.10, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issu
Change by E. Paine :
--
nosy: +serhiy.storchaka
versions: -Python 3.7
___
Python tracker
<https://bugs.python.org/issue42464>
___
___
Python-bugs-list mailin
Change by E. Paine :
--
components: +Library (Lib)
nosy: +pmoody
versions: +Python 3.10 -Python 3.9
___
Python tracker
<https://bugs.python.org/issue42
E. Paine added the comment:
You make very good points but sadly it is not that simple. The issue is
described in detail in the comment found in Modules/_tkinter.c:178. A good
summary is probably the comment for Tkapp_Call (Modules/_tkinter.c:1522
E. Paine added the comment:
I agree this is a race condition, and have narrowed the issue down to
wait_visibility with the following also hanging indefinitely (tested against
the master branch):
import threading
import tkinter as tk
def create_tp():
t = tk.Toplevel
E. Paine added the comment:
PR 23156 [Skip select ttk tests when on Ubuntu] proposes Ubuntu-specific test
skips and is given as a justification for PR 28468 [Add
platform.freedesktop_osrelease]. However, PR 23474 [Fix timeouts in ttk tests]
attempts to correctly address the issue, though
E. Paine added the comment:
> Could that bot be configured to run tests with -u-gui?
This has been found to not just affect one machine: it is both Azure and Github
Ubuntu. Therefore, the only Ubuntu bot still running gui tests would be Travis.
It could be done (with a very small pa
E. Paine added the comment:
Issue 42142 covers this problem. I want to get PR-23156 merged which will
(until a better fix is found) skip tests on Ubuntu which use `wait_visibility`.
However, this is becoming more of an issue and I am worried now about the
general stability of the tkinter
Change by E. Paine :
--
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue42351>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from E. Paine :
When compiling the master branch (i.e. running 'make'), I get a
UnicodeDecodeError as follows:
Traceback (most recent call last):
File "/home/elisha/Documents/Python/cp0/cpython/./setup.py", line 2619, in
main()
File "/home/elisha/Docum
E. Paine added the comment:
Sorry Brett to readd you to the nosy for this, but we only got half a sentence
in msg380718 (which is surely not what you intended?).
While I agree with you that this is not a bug, I do feel at least a note in the
docs would be helpful to explain the implications
E. Paine added the comment:
In short, the module isn't being added to the package's namespace because we
are directly modifying sys.modules (hence why the behaviour would be the same
if we imported using `import foo.b` as `from foo import b`).
I personally prefer to use the metapath instead
Change by E. Paine :
--
nosy: +epaine, gpolo, serhiy.storchaka
versions: +Python 3.10 -Python 3.7
___
Python tracker
<https://bugs.python.org/issue42305>
___
___
E. Paine added the comment:
This is starting to get *very* annoying. Today's failure was a new one (but
still `wait_visibility`):
test_variable_change (tkinter.test.test_ttk.test_extensions.LabeledScaleTest)
... Timeout (0:20:00)!
Thread 0x7f31dade1080 (most recent call first):
File
Change by E. Paine :
--
keywords: +patch
pull_requests: +22100
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23200
___
Python tracker
<https://bugs.python.org/issu
E. Paine added the comment:
> Most of them are in tests. There is no security issue there
TBH, I don't know enough about the exploit to comment, but it seems that the
tempfile tests take this seriously (Lib/test/test_tempfile.py:782 "For safety,
all use of mktemp must occur in a
Change by E. Paine :
--
components: +Distutils
nosy: +dstufft, eric.araujo
___
Python tracker
<https://bugs.python.org/issue42278>
___
___
Python-bugs-list mailin
E. Paine added the comment:
Just checking: is this not because the lazy import should be in `__init__.py`?
(the code provided works fine with `a.b.my_function` on my system)
--
components: +Interpreter Core -Library (Lib)
nosy: +brett.cannon, epaine, eric.snow, ncoghlan
type
New submission from E. Paine :
Currently, there are many uses of `tempfile.mktemp` in the stdlib. I couldn't
find an issue where this has already been discussed, but I think the usage of
mktemp in the stdlib should be completely reviewed. I grepped the Lib and a
slightly filtered version
E. Paine added the comment:
I have been looking for a more permanent solution to that proposed in PR-23156.
The most obvious solution is probably what I suggested in msg380371 as I don't
believe the calls to `wait_visibility` are required (though, I don't really
know enough to say
Change by E. Paine :
--
keywords: +patch
pull_requests: +22067
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23156
___
Python tracker
<https://bugs.python.org/issu
E. Paine added the comment:
I was wrong trying to blame Azure. I have now seen this happen on an Ubuntu
Github Action for PR-22947
(https://github.com/python/cpython/pull/22947/checks?check_run_id=1354118848).
test_virtual_event (tkinter.test.test_ttk.test_widgets.ComboboxTest) ...
Timeout
E. Paine added the comment:
For me, this is not limited to special characters. Trying to load anything in
Tk using the 'JoyPixels' font crashes (sometimes it does load but all
characters are very random - most are whitespace - and it crashes again after a
call to `fc-cache`). IDLE crashes
E. Paine added the comment:
This is strange as these only seem to have started occurring recently (though
there hasn't been a change to the tests themselves in a long time). There must
be something different about how Azure runs the GUI tests because it was on
Azure that the tests on PR
E. Paine added the comment:
If you had a bad update, it is likely your registry is corrupt. If at all
possible, I would recommend a Windows reinstall (it is quite likely other
software has also been affected). However, in the past I have had similar
problems and the Python installer does
E. Paine added the comment:
I am not touching the issue nosy and components for now but suspect this is a
Windows installation issue. As you said, there is no `idle.exe` file and
instead file association is done through a `idle.bat` file found at
Lib/idlelib/idle.bat. I have a few
Change by E. Paine :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<https://bugs.python.org/issue41
E. Paine added the comment:
I just confirmed (compiling the master having changed the system date) that
this double space does not occur when the date is double-digits (`Oct 10`),
suggesting that this is almost certainly intentional
E. Paine added the comment:
This has been an issue for a *long* time (issue 7676). Hopefully, the merging
of #37903 will allow this to be explored but currently there is not a lot that
can be done (without a serious refactor).
--
nosy: +epaine
New submission from E. Paine :
To elaborate on the information given in the title, @sy is referring to the
shell start text. More specifically, they are raising a grammatical issue with
`sys.version` where there are two spaces between the shortened month form and
the date (on my build
E. Paine added the comment:
Do we need to include the bitness (IDLE doesn't care)? On Windows, it will also
be included in the Python start-menu folder, so maybe we should consider moving
the bitness to the folder title (so the folder becomes "Python 3.8 64-bit")?
However, I
E. Paine added the comment:
Thank you for reporting this issue, however it is ultimately a Tk issue as
shown by running the attached script in wish. I assume the Tk version was
updated in Python 3.6, though I don't know which platform you are on so don't
know which of Ned or Steve to nosy
Change by E. Paine :
--
nosy: +epaine
___
Python tracker
<https://bugs.python.org/issue41896>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by E. Paine :
--
pull_requests: +21482
pull_request: https://github.com/python/cpython/pull/22453
___
Python tracker
<https://bugs.python.org/issue40
E. Paine added the comment:
I do think we should close the existing PR (TBH, I completely forgot about this
issue). Briefly looking again at the issue, it does indeed look like the GIL
hasn't seen the thread before the attempted call to restore the tstate (as
Steve said). If its alright
E. Paine added the comment:
Serhiy, while I agree this is an enhancement, I don't see that it would break
*anyone's* code (this will mostly just affect the REPL output) so is it worth
considering a backport?
Diohabara, the Python devguide (https://devguide.python.org/) is a very good
place
Change by E. Paine :
--
pull_requests: +21465
pull_request: https://github.com/python/cpython/pull/22434
___
Python tracker
<https://bugs.python.org/issue41
E. Paine added the comment:
> Why would negating the font size convert it from points to pixels??
Oh... I apologise: I clearly didn't think this through. It doesn't "convert" in
any sense, it just negates the font size so 16 points becomes 16 pixels.
Therefore, it is practi
New submission from E. Paine :
I think it would be helpful to add these methods to the tkinter font class.
Starting with the equal method, I have found it very useful to be able to
compare tkinter fonts based on their value rather than just name. I used this,
for example, in #28694 to ensure
Change by E. Paine :
--
keywords: +patch
pull_requests: +21436
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22396
___
Python tracker
<https://bugs.python.org/issu
E. Paine added the comment:
I have started looking at Mark's wrapper (though I have not been able to
spend as much time on it as I would like). It's mostly small changes
that I have made (in no particular order):
- TkFontchooserFontChanged event calls 'command' (to be behave like an
'apply
E. Paine added the comment:
Thank you for reporting this. Please could you double check what you ran
because your code says 'st_file_attributes' but the error says
'st_file_atributes' (missing a t in attributes).
--
nosy: +epaine
___
Python
Change by E. Paine :
--
assignee: -> terry.reedy
components: +IDLE
nosy: +epaine
versions: +Python 3.10 -Python 3.7
___
Python tracker
<https://bugs.python.org/issu
E. Paine added the comment:
+1 I also think that the fontchooser should be wrapped. I briefly tested your
wrapper, Lance, and found it worked fine on Windows but did not on my Linux
setup (because it is non-modal).
I went about implementing my own wrapper based loosely around your's (see
E. Paine added the comment:
Firstly, apologies about the original message: rereading it, it was a bit
random and written in a very illogical order.
> Are you the Elisha Paine that suggested the original fix?
Yes (though I like to think I have somewhat progressed in 2 years!). The reason
E. Paine added the comment:
Thank you for reporting this issue. I wanted to start by pointing out a finer
detail: the XFCE program title on the task switcher (the thing you're reporting
and I don't have a clue how to describe) is not the same as the default window
title (the program title
New submission from E. Paine :
Following #33656, IDLE now "lies" to Windows and declares it has system DPI
awareness to achieve a *sharper* look. System dpi is in effect:
DPI_AWARENESS_UNAWARE * Windows' zoom factor
Therefore, for IDLE to scale to the Windows' zoom/scale fact
E. Paine added the comment:
As I believe planning for removal (including the version this should occur in)
is better suited to #31371, I think it would be best to remain non-committal
about the version. I would personally prefer something a little more vague
(such as below), though as I
E. Paine added the comment:
+1
I think this would be very helpful as the only places I can find its
deprecation are a small note at the top of the Tix Python docs
[https://github.com/python/cpython/commit/bd63353] and a news entry a long way
down the 3.6 release notes https
E. Paine added the comment:
Thank you for reporting this bug (particularly for the detailed instructions
for reproduction). This has already been fixed in #41373 just over a month ago,
and is already available in the 3.9 release candidate (though the fix will not
be released for 3.8 until
E. Paine added the comment:
I am struggling to reproduce. On Linux the window shows exactly as expected (it
does take a while to close, though, which is understandable) and on Windows the
window never shows (it gets stuck before the mainloop). This is, however, not a
tkinter problem as I
E. Paine added the comment:
I have updated the PR for the following two suggestions:
> I would rather trailing blocks be deleted all at once
> Anything after [the prompt] is an indent and should be treated as such
Again, consider the following examples (apologies about the last ones:
E. Paine added the comment:
Further clarification on the new behaviour: in the shell whitespace after the
prompt (>>>) will not be considered an indent and only have one character
deleted at a time. However, on a continuation line, any initial whitespace will
be considered
Change by E. Paine :
--
keywords: +patch
pull_requests: +21048
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21934
___
Python tracker
<https://bugs.python.org/issu
New submission from E. Paine :
I could not think of a better title so will attempt to explain myself better
here. Currently, the IDLE smart backspace will delete multiple whitespace up to
the tab width even if it is not at the start of the line. Consider the
following examples (where
E. Paine added the comment:
Ned, does it appear like Python is using the MacOS built-in Tcl version? My
(very limited) understanding is that Python will default to the Tcl version
packaged with it (which is currently 8.6.8).
--
___
Python tracker
E. Paine added the comment:
To help us to reproduce the issue, please give your Python version, Tcl/Tk
patchlevel (`tkinter.test.support.get_tk_patchlevel()`), MacOS version and a
small demonstration script (along with exact keystrokes/clicks if necessary). I
suspect this is another Tcl/Tk
E. Paine added the comment:
Thank you Cheryl for linking this issue on #40468 (I didn't find this when
researching for existing issues). I have briefly tested the PR and it seems
perfect, though seeing `init_validators` made me think we should possibly have
an ABC for the tab pages
E. Paine added the comment:
Would you mind please checking if #41373 is the problem you describe?
(apologies about this issue, we are having relatively lots of reports about it
but the fix won't be distributed until 3.9.0/3.8.6)
--
nosy: +epaine
E. Paine added the comment:
Reflecting on #41522, I decided that it would be best to work on this issue
before going any further with that one (partly because it would require us to
redo some of the work and also because this issue should have a higher
priority). I have put together
New submission from E. Paine :
Currently, the tabs on the configdialog's Notebook only have a text
description. I propose we add icons to the tabs to make them a little more
colourful, new-user-friendly, etc.
I have drafted a version which uses icons found in the Public Domain (I can
E. Paine added the comment:
Sorry for this issue, IDLE 3.8.5 has a known (and now resolved) issue with
saving if the file was empty when opened (see #41373). If this is not your
problem, please do come back and say so, but otherwise this issue should be
closed as a duplicate
E. Paine added the comment:
To help us to reproduce and understand the issue, please could you give us 1) a
more detailed explanation of the problem you are facing and 2) steps to
reproduce the issue (maybe providing a minimal code example if that is the
cause). Is this a bug with IDLE
E. Paine added the comment:
For reference, I have opened
https://core.tcl-lang.org/tk/tktview?name=81c3ef93148d17ff280d9a0b4c4edfce453b972f
to report this to the Tk team and ask if this change in behaviour is intended.
--
___
Python tracker
Change by E. Paine :
--
keywords: +patch
pull_requests: +20859
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/21715
___
Python tracker
<https://bugs.python.org/issu
E. Paine added the comment:
+1 this issue. I have encountered this problem lots when testing patches and
almost always just end up deleting the test_from method to get test_tk to pass.
I am not sure of a solution, though, as we *need* to keep test compatibility
with Tk 8.6.8 while
E. Paine added the comment:
> but not with binding to modifier-up/down.
I cannot reproduce. I have tested on both Windows and Linux and found I could
successfully change to (and use) the modifier-up/down bindings both through the
Keys page of the configdialog and by editing the keys
E. Paine added the comment:
Thanks Steve for your explanation. I had a quick experiment with the
ENTER_PYTHON definition and initially just added a call to PyThreadState_Get if
the tstate was NULL. This still crashed the interpreter with the following
error (which I think reaffirms Steve's
101 - 200 of 294 matches
Mail list logo
