New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Tkinter) Please backport these #48592
Comments
Please consider backporting r59653 and r59654 to release25-maint branch. It may be of interest to backport r52688 too, also, r63776 together with Finally there is this bpo-4333 which wasn't committed anywhere, but if Thanks. |
I'm skeptical about backporting r59654. Doing so might break existing |
Can you remind me what problem was fixed with r59653? I can't find the If it fixes a problem with supporting Tcl 8.5, then I will also reject |
On Wed, Dec 10, 2008 at 6:15 AM, Martin v. Löwis <report@bugs.python.org> wrote:
I don't see in what way it would break existing applications. The |
On Wed, Dec 10, 2008 at 6:21 AM, Martin v. Löwis <report@bugs.python.org> wrote:
I had trouble finding it too, it was redirected to somewhere else and
But if it doesn't affect anything in the current usage, why not |
I can't quite follow your terminology: what indices? I can imagine many cases where conversion using Python's str() gives If you are saying that the Python command *should* return strings |
On Fri, Dec 12, 2008 at 9:06 PM, Martin v. Löwis <report@bugs.python.org> wrote:
Are we talking about the same commit ? 59654 as in your original about |
Oops, no. I now see that r59654 is fine for backporting. My last message The other changes seem to introduce new features, so they are out of |
I have backported r59654 as r67737. As indicated, the other patches are |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: