Berker Peksag added the comment:
Hi Claudiu, thanks for the report, but I don't think this is a common use case
that needs to be supported in the standard library. Other people may prefer to
use different solutions in a similar case (e.g. using a debugger) Plus, it's
not hard to implement
Berker Peksag added the comment:
This is a duplicate of issue 11341.
--
nosy: +berker.peksag
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> test_os fails
___
Python tracker <rep...@bugs.py
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
versions: -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Berker Peksag added the comment:
Good catch, thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
versions: +Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.py
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thanks for the report! I've now updated the example to use MessageBoxw.
Eryk, do you find the second example (GetWindowRect) is useful? Can we make it
more usable? Unless I'm missing something, we need to pass the return value of
GetActiveWindow() to make
Berker Peksag added the comment:
> What is the process? hg clone cpython, and make a patch from that and post it
> here?
Yes, it's exactly what you just described :) See
https://docs.python.org/devguide/index.html for details.
> Or is there some pull-request style process available?
Berker Peksag added the comment:
The culprit is the ``test_suite='nose.collector'`` line here. It looks like
this has already been fixed in nose:
https://github.com/nose-devs/nose/issues/759
--
nosy: +berker.peksag
resolution: -> not a bug
stage: -> resolved
status: open -&g
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
nosy: +berker.peksag
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
keywords: +easy
nosy: +berker.peksag
stage: -> needs patch
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> fixed
stage: needs patch -> resolved
status: pending -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Berker Peksag added the comment:
+1 from me. This would help people to port their projects to Python 3.
--
nosy: +berker.peksag
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
Here's an updated patch.
--
Added file: http://bugs.python.org/file44849/issue27322_v3.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
Just saw
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.x%203.5/builds/1136/steps/test/logs/stdio
and went ahead to remove the test.
--
resolution: -> fixed
stage: needs patch -> resolved
status: open -&g
Berker Peksag added the comment:
test_sock_connect_sock_write_race failure is being discussed in issue 28283.
Closing this again.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://
Berker Peksag added the comment:
Perhaps running a script like below on the host would help to identify the
problem?
import getpass
import grp
import pprint
pprint.pprint(getpass.getuser())
pprint.pprint([(g.gr_gid, g.gr_name) for g in grp.getgrall()])
pprint.pprint([(g.gr_gid, g.gr_name
Berker Peksag added the comment:
Thanks for triaging this, Bert. Would you like to propose a patch with a test
case?
Note that we can't fix this in 3.3 and 3.4 because they are in
security-fix-only mode. See
https://docs.python.org/devguide/index.html#status-of-python-branches for
details
Berker Peksag added the comment:
I think we can add a note for starmap() in the following sentence:
> [...] (it supports only one iterable argument though).
(Quoted from
https://docs.python.org/3/library/multiprocessing.html#multiprocessing.pool.Pool.map)
Would you like to write a pa
Berker Peksag added the comment:
> If nobody fixes the unit test, I will revert the change.
I attached a patch that skips the test in case of a timeout in issue 28176. Did
you had a chance to take a look at it?
--
nosy: +berker.peksag
stage: -> needs patch
type: -> behavior
Berker Peksag added the comment:
Serhiy's patch looks good to me. It would be nice to add a test for multiple
invalid keyword arguments:
with self.assertRaisesRegex(TypeError, msg):
ImportError('test', invalid='keyword', another=True)
Using empty_tuple seems reasonable to me
Berker Peksag added the comment:
Please note that Python/Python-ast.c is automatically generated by
Parser/asdl_c.py.
--
nosy: +benjamin.peterson, berker.peksag
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Berker Peksag added the comment:
Thanks, Tom.
--
components: -Library (Lib)
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Berker Peksag added the comment:
Instead of duplicating XML() documentation, I'd suggest changing fromstring()
documentation to say something like "this is an alias for ElementTree.XML()."
--
nosy: +berker.peksag
versions: +Python 3.5,
Berker Peksag added the comment:
Fixed. I lost some time because of this today :)
--
nosy: +berker.peksag
resolution: -> fixed
stage: test needed -> resolved
status: open -> closed
versions: +Python 3.7 -Python 3.4
___
Python tra
Berker Peksag added the comment:
Unless I'm missing something, this is a duplicate of issue 17218 :)
--
nosy: +berker.peksag
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> support title and description in argparse
add_mutually_exc
Berker Peksag added the comment:
Thanks for the patch. We can't fix this in 3.4 because it's in
security-fix-only mode:
https://docs.python.org/devguide/index.html#status-of-python-branches
--
versions: -Python 3.4
___
Python tracker <
Berker Peksag added the comment:
Serhiy, do you have further comments about issue26868_v2.diff?
--
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
Thanks Victor!
--
stage: needs patch -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
nosy: -SH4Y4N
title: very useful information -> Spam
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
I think the problem described in msg270181 is now fixed in issue 24022. Adding
Benjamin to nosy list for the other case.
--
nosy: +benjamin.peterson, berker.peksag
___
Python tracker <rep...@bugs.python.org>
Berker Peksag added the comment:
Thanks for the report. This looks like a duplicate of issue 24022.
--
nosy: +berker.peksag
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Python heap corruption issue
__
Berker Peksag added the comment:
Please upload your patch from a Mercurial clone:
* https://docs.python.org/devguide/setup.html#checkout
* https://docs.python.org/devguide/patch.html
Currently, if you pass a string as a second argument, you get:
>>> complex(1, "1")
Tracebac
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Changes by Berker Peksag <berker.pek...@gmail.com>:
Added file: http://bugs.python.org/file44740/issue25400_v3.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Berker Peksag added the comment:
Here's an updated patch.
--
versions: +Python 3.7
Added file: http://bugs.python.org/file44739/issue25400_v2.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
For some reason, some tests fail randomly on FreeBSD buildbots. See also
issue27784. I'm planning to apply the attached patch.
--
keywords: +patch
nosy: +koobs
Added file: http://bugs.python.org/file44736/issue28176_skip_tests.diff
Berker Peksag added the comment:
It looks like
http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/11581 is
first time that the test was failed.
Revisions (without documentation changes) in that build:
* 378e000a68785fdb3d74b3a930bc4ac5f6a04ce5
Berker Peksag added the comment:
test_robotparser is now green. I've opened issue 28195 for
test_huntrleaks_fd_leak.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.pytho
New submission from Berker Peksag:
>From
>http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/11654/steps/test/logs/stdio
==
FAIL: test_huntrleaks_fd_leak (test.test_regrtest.ArgsTe
Berker Peksag added the comment:
This looks like a bug in ncurses 5.7 and a duplicate of issue 15037.
--
nosy: +berker.peksag
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> curses.unget_wch and test_curses fail when linked with
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Changes by Berker Peksag <berker.pek...@gmail.com>:
Added file: http://bugs.python.org/file44721/issue26384_v3.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Berker Peksag added the comment:
Thanks, Serhiy. Here's an updated patch.
--
versions: +Python 3.7
Added file: http://bugs.python.org/file44720/issue26384_v2.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
This is resolved by issue 28075.
--
nosy: +berker.peksag
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thanks, Eryk.
--
nosy: +berker.peksag
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thanks for the review, Serhiy! Good point, closing this as 'not a bug'.
--
resolution: -> not a bug
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.pytho
Berker Peksag added the comment:
What do you mean by crash? I think the purpose of the test is to crash the
interpreter:
def test_recursionlimit_fatalerror(self):
# A fatal error occurs if a second recursion limit is hit when
recovering
# from a first one
Berker Peksag added the comment:
Thanks for the patch. I left some comment on Rietveld:
http://bugs.python.org/review/26149/#ps18589
--
stage: needs patch -> patch review
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org&
Berker Peksag added the comment:
Would increasing timeout to 10.0 be sufficient? Should we wrap the test with
@support.reap_threads?
--
nosy: +berker.peksag
status: pending -> open
versions: +Python 3.5, Python 3.7
___
Python tracker &
Changes by Berker Peksag <berker.pek...@gmail.com>:
Added file: http://bugs.python.org/file44711/pybytes_resize_regenerated.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Berker Peksag:
There are a couple of instances that don't check return value of
_PyBytes_Resize in Modules/. I noticed this while working on issue 25270.
Patch attached.
--
components: Extension Modules
files: pybytes_resize.diff
keywords: patch
messages: 276778
Berker Peksag added the comment:
Here's a patch that uses pythontest.net.
--
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file44695/issue28151.diff
___
Python tracker <rep...@bugs.python.org&
Berker Peksag added the comment:
Thanks for the reviews everyone!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thank you Gergely and Markus!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thanks for the review, Serhiy. Here's an updated patch.
--
Added file: http://bugs.python.org/file44691/issue25270_v3.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
3.4 is in security-fix-only mode so it doesn't get bugfix updates anymore.
--
nosy: +berker.peksag
resolution: -> out of date
status: open -> closed
versions: +Python 3.5
___
Python tracker <rep...@bugs.p
Berker Peksag added the comment:
Here is an updated patch.
--
versions: +Python 3.7
Added file: http://bugs.python.org/file44689/issue25270_v2.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Berker Peksag <berker.pek...@gmail.com>:
Added file: http://bugs.python.org/file44688/full_output.txt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Berker Peksag:
This is a follow-up from msg275748 in issue 27213 (Rework CALL_FUNCTION*
opcodes). I believe the test_runpy failure I mentioned there is also the same
error, but this one can be reproduced easily.
test_recursionlimit_fatalerror in SysModuleTest (Lib/test
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thanks for the patch, Eryk!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
I think the current consensus is to keep old APIs around to make porting from
Python 2 easier. That's why I opened issue 26041.
See also msg256111 and "Deprecation policy PEP" proposed at
https://mail.python.org/pipermail/python-committers/2016-Janu
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
nosy: +orsenthil
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27973>
___
Berker Peksag added the comment:
Thanks for the report. This was already done in Python 3.4. See
https://docs.python.org/dev/whatsnew/3.4.html#changes-in-python-command-behavior
and issue 18338 for details. Backporting this to 2.7 would break backwards
compatibility so that means we can't
Berker Peksag added the comment:
Eryk's patch looks good to me, thanks! I will wait for others to review the
patch.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
versions: +Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Berker Peksag added the comment:
Note that I'm planning to rewrite the test to use pythontest.net.
--
nosy: +berker.peksag
stage: -> needs patch
type: -> enhancement
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.o
Berker Peksag added the comment:
Can you wrap the test with @support.cpython_only decorator? The patch fixes the
memory leak demonstrated in test-dict-pop.py.
--
nosy: +berker.peksag, haypo, methane
stage: -> patch review
___
Python tracker &
Berker Peksag added the comment:
Thanks!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7 -Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
nosy: +steve.dower, zach.ware
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Berker Peksag added the comment:
Here's a patch for Unix. I will add Windows support when I get my Windows VM.
> [...] (and add a test - test_crashers, presumably?) [...]
Unfortunately, test_crashers doesn't run since 2011 (skipped in 481ad9129a0f.)
parse_envlist() is only used by os.exe
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Thanks for the report and for the reviews!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Here is a patch with a test case.
--
keywords: +patch
nosy: +berker.peksag
stage: -> patch review
type: -> behavior
Added file: http://bugs.python.org/file44647/issue28131.diff
___
Python tracke
Berker Peksag added the comment:
Victor committed the patch in msg276042 in 579141d6e353.
--
nosy: +berker.peksag
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Berker Peksag added the comment:
Here is a patch that reuses the helper in CommandLineTests.
--
nosy: +berker.peksag
stage: needs patch -> patch review
versions: +Python 3.5, Python 3.7
Added file: http://bugs.python.org/file44621/issue27322_v2.d
Berker Peksag added the comment:
Thanks for the updated patches. Since they both intend to fix the same problem,
we can combine them in one patch file.
--
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org&
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
nosy: +ncoghlan, rhettinger
stage: -> needs patch
versions: -Python 3.3, Python 3.4, Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Berker Peksag added the comment:
Done. I'm going to pretend 2.7 doesn't exist :)
--
nosy: +berker.peksag
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Berker Peksag added the comment:
Thanks for the patch, David!
--
components: +Interpreter Core
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
versions: +Python 3.5, Python 3.7
__
Berker Peksag added the comment:
I think a Misc/NEWS entry is enough. We didn't use versionadded/versionchanged
directives for similar changes in the past (mimetypes.types_map for example)
Even if we decide to add an annotation it should be versionchanged, not
versionadded (the API is not new
Berker Peksag added the comment:
The patch doesn't apply cleanly:
applying
http://bugs.python.org/file37554/distutils_accomodate_distribution_ducktypes.patch
patching file Lib/distutils/cmd.py
Hunk #1 FAILED at 51
1 out of 1 hunks FAILED -- saving rejects to file Lib/distutils/cmd.py.rej
abort
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
versions: +Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Berker Peksag added the comment:
This is a duplicate of issue 17232. Note that "This changes the filename
extension for compiled files from ``.pyc`` to ``.pyo``." part is no longer
true. See PEP 488 for details.
--
nosy: +berker.peksag
resolution: -> duplicate
stage:
Berker Peksag added the comment:
Good catch, thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: enhancement -> behavior
versions: -Python 2.7, Python 3.3, Python 3.4, Python 3.7
___
Py
Berker Peksag added the comment:
Tom's patch looks good to me. Davin, can you have a look at it?
--
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Berker Peksag added the comment:
Thanks for the explanation. We usually handle situations like this in the same
issue so I'm closing this as a duplicate of issue 10673. Could you please
attach your patch to issue 10673? Thanks!
--
resolution: -> duplicate
stage: -> resolved
Berker Peksag added the comment:
Hi Tom, thanks for the patch! Issue 10673 is still open, is there a reason not
to attach your patch there?
--
nosy: +berker.peksag
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Berker Peksag added the comment:
Since we are going to move to GitHub, I think we can close this as 'wont fix'.
--
nosy: +berker.peksag
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bug
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Berker Peksag added the comment:
Since PEP 442 has been implemented in 3.4 and e826940911c8 made Shelve.close()
more robust, I think this is no longer an issue.
--
nosy: +berker.peksag
resolution: -> out of date
stage: patch review -> resolved
status: open -&g
Berker Peksag added the comment:
3.2 is now dead and it's probably not worth to backport tests to 2.7 in 2016 :)
Closing this as 'fixed'.
--
nosy: +berker.peksag
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
versions: +Python 3.3 -Python 2.7, P
Changes by Berker Peksag <berker.pek...@gmail.com>:
--
nosy: +haypo
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28081>
___
_
1401 - 1500 of 3698 matches
Mail list logo
