Berker Peksag added the comment:
Thanks for the report. Yes, the RawConfigParser change was intentional and it
was discussed in issue 20120. I'm marking this as a documentation issue.
--
assignee: -> docs@python
components: +Documentation
nosy: +berker.peksag, docs@pyth
Berker Peksag added the comment:
Issue 26537 is a duplicate of this one but it has an up-to-date and more
complete patch so I'm going to close this one.
--
nosy: +berker.peksag
resolution: -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder: -
Berker Peksag added the comment:
I was thinking to document issue 20120 in Misc/NEWS. It turns out I was looking
at the wrong commit and it was already documented in eae59b6bf133.
--
resolution: -> not a bug
stage: needs patch -> resolved
status: open -&g
Changes by Berker Peksag :
Removed file: http://bugs.python.org/file43674/b3b439d7dd40.diff
___
Python tracker
<http://bugs.python.org/issue23285>
___
___
Python-bug
Changes by Berker Peksag :
--
components: -Installation, Interpreter Core, Library (Lib), Tests
type: performance -> compile error
versions: -Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Changes by Berker Peksag :
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
type: behavior -> enhancement
___
Python tracker
<http://bugs.python
Changes by Berker Peksag :
--
resolution: -> out of date
stage: needs patch -> resolved
type: -> behavior
versions: -Python 3.4
___
Python tracker
<http://bugs.python.or
Changes by Berker Peksag :
--
Removed message: http://bugs.python.org/msg270204
___
Python tracker
<http://bugs.python.org/issue16858>
___
___
Python-bugs-list m
Changes by Berker Peksag :
--
Removed message: http://bugs.python.org/msg265967
___
Python tracker
<http://bugs.python.org/issue16858>
___
___
Python-bugs-list m
Changes by Berker Peksag :
--
Removed message: http://bugs.python.org/msg270206
___
Python tracker
<http://bugs.python.org/issue16858>
___
___
Python-bugs-list m
Berker Peksag added the comment:
logging module doesn't support Path objects. You need to wrap
STATUSLOG_PATH = Path('~/logFiles/Reseller/').expanduser()
with str().
We could possibly add PEP 519 support to the logging module for Python 3.6.
What do you think, Vinay?
Changes by Berker Peksag :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue27504>
___
___
Changes by Berker Peksag :
--
keywords: +easy
nosy: +berker.peksag
stage: -> needs patch
type: enhancement -> behavior
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/i
Changes by Berker Peksag :
--
nosy: +andymaier, belopolsky, docs@python, eric.araujo, ezio.melotti,
georg.brandl, lukasz.langa, rhettinger, terry.reedy -lissacoffeyx
___
Python tracker
<http://bugs.python.org/issue10
Changes by Berker Peksag :
--
Removed message: http://bugs.python.org/msg270297
___
Python tracker
<http://bugs.python.org/issue10225>
___
___
Python-bugs-list m
Berker Peksag added the comment:
Since 2e29d54843a4 this is no longer needed. Thanks for the patches!
--
nosy: +berker.peksag
resolution: -> out of date
stage: patch review -> resolved
status: open -> closed
___
Python track
Berker Peksag added the comment:
By the way, there is an open ticket about changing the recipe in Django
documentation: https://code.djangoproject.com/ticket/26040
--
nosy: +berker.peksag
___
Python tracker
<http://bugs.python.org/issue27
Berker Peksag added the comment:
Since Terry is already busy with IDLE maintenance, I went ahead and commit the
patch with minor modifications. Thanks for the patch, John! :)
--
resolution: -> fixed
stage: patch review -> resolved
status: open -&g
Berker Peksag added the comment:
Thanks!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Berker Peksag added the comment:
Sorry, I finally found some time to clear my CPython TODO list. Thanks for the
patch, Evelyn!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python track
Changes by Berker Peksag :
--
stage: patch review -> resolved
title: [PATCH] Tests break with --with-system-expat and Expat 2.2.0 -> Tests
break with --with-system-expat and Expat 2.2.0
___
Python tracker
<http://bugs.python.org/i
Berker Peksag added the comment:
> This patch adds a test but does not fix the bug.
I forgot to explain what the first patch does. The specific problem reported by
OP has already been fixed in default branch (but not in 3.5) so issue18858.diff
was added a test to make sure that threading
Berker Peksag added the comment:
Thanks, Stéphane.
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
versions: +Python 3.5
___
Python tracker
<http://bugs.python
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
Changes by Berker Peksag :
--
versions: -Python 3.5, Python 3.6
___
Python tracker
<http://bugs.python.org/issue27519>
___
___
Python-bugs-list mailing list
Unsub
Berker Peksag added the comment:
Thanks for the patches! Can't you just use a function from the high level
subprocess API (like subprocess.run()?
--
stage: -> patch review
versions: +Python 3.6 -Python 3.4
___
Python tracke
Berker Peksag added the comment:
I was talking about webbrowser.py-3.4-newfox.patch
3.4 is now in security-fix-only mode so we can't push the patch to the 3.4
branch.
--
___
Python tracker
<http://bugs.python.org/is
Berker Peksag added the comment:
I'm getting a segfault after d87f99e297d5 (SubinterpreterTest.test_subinterps).
$ ./python -m test test_capi
Run tests sequentially
0:00:00 [1/1] test_capi
Fatal Python error: Segmentation fault
Current thread 0x7fd5e401d700 (most recent call first):
Berker Peksag added the comment:
Good catch, thanks Michael!
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
Changes by Berker Peksag :
--
resolution: remind -> not a bug
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue27559>
___
___
Python-bugs-
Berker Peksag added the comment:
I would prefer Antti's test case in msg270730 since the bug can be reproduced
by using threading module (you can use assert_python_ok() as a helper.)
Lib/test_threading.py is probably a better place for the test.
--
nosy: +berker.peksag
stage:
Changes by Berker Peksag :
--
nosy: +orsenthil
stage: -> patch review
type: enhancement -> security
versions: +Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6
___
Python tracker
<http://bugs.python.org/i
Berker Peksag added the comment:
Thanks!
--
nosy: +berker.peksag
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue27567>
___
___
Python-
Berker Peksag added the comment:
-1
I think the current devguide theme looks fine and it would be nice to keep
devguide and Python documentations use different themes.
I'd be -0 if the patch was small, but diff stat "11 files changed, 1651
insertions(+), 10 deletions(-)" is hu
Berker Peksag added the comment:
Can we at least serve images and JS files (py.png -- this gives 404 now,
copybutton.js, sidebar.js) from docs.python.org?
It seems like devguide_theme_revised.patch was committed accidentally:
https://hg.python.org/devguide/rev/9e7b1bc15ba7#l3.3
The color of
Berker Peksag added the comment:
This looks like a duplicate of issue 2382.
--
nosy: +berker.peksag
___
Python tracker
<http://bugs.python.org/issue27582>
___
___
Berker Peksag added the comment:
Attached patch adds tests for common members of Lib/genericpath.py.
--
keywords: +patch
nosy: +berker.peksag
stage: needs patch -> patch review
versions: +Python 3.6 -Python 3.4
Added file: http://bugs.python.org/file43821/issue13849.d
Berker Peksag added the comment:
LGTM
--
assignee: -> berker.peksag
components: +Extension Modules
nosy: +berker.peksag
stage: -> patch review
type: -> behavior
versions: +Python 3.5
___
Python tracker
<http://bugs.python.or
Berker Peksag added the comment:
Yes, that's why I assigned it to myself :) Thanks for the patch!
--
___
Python tracker
<http://bugs.python.org/is
Berker Peksag added the comment:
> V547 Expression 's->sock_fd < 0' is always false. Unsigned type value is
> never < 0. Modules/socketmodule.c:655
> V547 Expression 's->sock_fd < 0' is always false. Unsigned type value is
> never < 0. Module
Changes by Berker Peksag :
--
components: +Interpreter Core -Library (Lib)
nosy: +berker.peksag
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issu
Berker Peksag added the comment:
Here is an updated patch. Thanks, Victor.
--
Added file: http://bugs.python.org/file43837/issue27591_v2.diff
___
Python tracker
<http://bugs.python.org/issue27
Berker Peksag added the comment:
Thanks! I should read PEP 7 again :)
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Berker Peksag added the comment:
Thanks for your review, Victor. I don't care about 2.7 at this point so I went
with 3.5+ :)
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http:
Changes by Berker Peksag :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue27493>
___
___
Python-bugs-list mailing list
Unsubscrib
Berker Peksag added the comment:
Thanks!
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Berker Peksag added the comment:
Merged in f4fe55dd5659.
--
nosy: +berker.peksag
stage: -> resolved
status: open -> closed
type: -> behavior
versions: +Python 3.5, Python 3.6
___
Python tracker
<http://bugs.python.or
Berker Peksag added the comment:
Looks good to me too. 'hash_value' looks more readable to me, thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
type: -> behavior
versions: -Python 3.2,
Berker Peksag added the comment:
I'm attaching Christian's patch at
https://marc.info/?l=python-dev&m=146922730716425&w=2 as
issue27587_pystate_addmodule.diff to make code reviewing easier.
--
stage: needs patch -> patch review
_
Changes by Berker Peksag :
--
keywords: +patch
Added file: http://bugs.python.org/file43870/issue27587_pystate_addmodule.diff
___
Python tracker
<http://bugs.python.org/issue27
Berker Peksag added the comment:
> I am very sorry, this is probably my fault.
It's not your fault :) I removed them.
3.2, 3.3 and 3.4 are in security-fix-only mode so they won't get any
documentation updates. You can read
https://docs.python.org/devguide/devcycle.html#secbranc
Berker Peksag added the comment:
I left some review comments on Rietveld. I think we can treat this as a bug and
fix it in 3.5 too.
--
nosy: +berker.peksag
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issu
Berker Peksag added the comment:
Thanks for the report and for the patch, Aleksandr. This is a duplicate of
issue 20825. See also issue 27628 for a similar report.
--
dependencies: -speed up ipaddress __contain__ method
nosy: +berker.peksag
resolution: -> duplicate
stage: pa
Berker Peksag added the comment:
See also issue 25431.
--
___
Python tracker
<http://bugs.python.org/issue27628>
___
___
Python-bugs-list mailing list
Unsub
Changes by Berker Peksag :
--
nosy: +berker.peksag
versions: +Python 3.5, Python 3.6 -Python 3.2, Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issue11
Berker Peksag added the comment:
Good catch, thanks!
--
nosy: +berker.peksag
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
type: enhancement -> behavior
versions: -Python 3.3, Python 3.4
___
Python tr
Berker Peksag added the comment:
There is no need to go to python-ideas for this. Adding domain experts to nosy
list is enough.
--
nosy: +berker.peksag, mark.dickinson, serhiy.storchaka
___
Python tracker
<http://bugs.python.org/issue27
Berker Peksag added the comment:
Thanks for the patch! I haven't had a chance to review the patch yet, but we
also need documentation updates to Doc/library/sqlite3.rst.
--
nosy: +berker.peksag
stage: -> patch review
___
Python tracke
Berker Peksag added the comment:
This was marked as 'fixed' almost two years ago. I tried to install 3.4.3,
uninstall 3.4.3 and install 3.4.4 again in Win 10 and it worked fine for me. I
guess this was left open accidentally.
--
nosy: +berker.peksag
status: open
Berker Peksag added the comment:
This has already been backported to 2.7 in issue 24508.
--
nosy: +berker.peksag
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Berker Peksag added the comment:
Sorry, I'm a bit late to the party. Here are some tweaks to ecc7bff738e0. I've
added versionadded directives, updated the tests to use new style classes and
removed a duplicate sentence from the __init_subclass__ docstring.
--
Added
Berker Peksag added the comment:
Looks good to me, thanks!
--
nosy: +berker.peksag
stage: -> commit review
title: [Patch] Make use of non-standard error number ESHUTDOWN optional -> Make
use of non-standard error number ESHUTDOWN optional
type: -> en
Berker Peksag added the comment:
Thanks for the review, Nick! (and also thanks to Martin for the great PEP!)
--
___
Python tracker
<http://bugs.python.org/issue27
Berker Peksag added the comment:
Thanks again, Ed! Could you please sign the PSF contributor agreement at
https://www.python.org/psf/contrib/contrib-form/ ?
Also, you don't need to strip out the header part of the patch file (Mercurial
didn't recognize it as a valid patch file). Yo
Changes by Berker Peksag :
--
nosy: +berker.peksag
___
Python tracker
<http://bugs.python.org/issue19660>
___
___
Python-bugs-list mailing list
Unsubscribe:
Berker Peksag added the comment:
Thread.join() also returns None in all cases so +1 for documenting the current
behavior.
--
keywords: +easy
nosy: +berker.peksag
stage: -> needs patch
versions: +Python 3.5, Python 3.6 -Python 3.3
___
Python trac
Changes by Berker Peksag :
--
stage: patch review -> resolved
___
Python tracker
<http://bugs.python.org/issue27568>
___
___
Python-bugs-list mailing list
Un
Changes by Berker Peksag :
--
components: -Library (Lib)
keywords: +easy
stage: -> needs patch
type: -> enhancement
versions: +Python 3.6 -Python 3.4
___
Python tracker
<http://bugs.python.org/i
Berker Peksag added the comment:
Thanks for the report. The stdlib version of subprocess module has a little bit
codebase now (there is no subprocess_cloexec_pipe() routine anymore, for
example) so we can't do anything here. Could you please report this to
https://github.com/google/p
Berker Peksag added the comment:
The test code in issue27558_v2.patch looks OK to me.
--
___
Python tracker
<http://bugs.python.org/issue27558>
___
___
Python-bug
Berker Peksag added the comment:
Py_WINVER has been updated to use 0x0600 (_WIN32_WINNT_VISTA) in 57e2549cc9a6
(issue 23451) Since the consensus was to keep 2.7 as is I'm closing this as
'out of date'.
--
nosy: +berker.peksag
resolution: -> out of date
stage: needs
Changes by Berker Peksag :
--
nosy: +berker.peksag
stage: -> patch review
versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Berker Peksag added the comment:
The patch looks good to me. Note that the patch in issue 24278 also removes the
same note.
--
nosy: +berker.peksag
stage: -> patch review
type: -> behavior
versions: +Python 3.5, Python 3.6 -Python 3.4
___
Berker Peksag added the comment:
Thanks for the report. This has already been fixed in 4f5e4155c259 ( Python
3.5+)
--
nosy: +berker.peksag
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python track
Berker Peksag added the comment:
> It also indents the attributes and descriptions to emphasize that they are
> part of the UUID instance, not the uuid module.
Thanks for the patch, but please revert unrelated changes.
--
nosy: +berker.peksag
stage: needs patch -> pat
Berker Peksag added the comment:
Thanks for the patch, Chris. I've only changed `func` to ``func`` (we don't use
single backtick in reST.)
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> enhancement
versions: +
Berker Peksag added the comment:
I wouldn't consider it a problem since both forms are supported. Also note that
you don't need to specify the "UUID." prefix when you use the indented form:
.. class:: UUID(...)
.. attribute:: bytes
I don't think the
Berker Peksag added the comment:
Thanks for the patch. Committed capidocs.diff-2 with some tweaks.
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Berker Peksag :
--
nosy: -luisa.sam...@gmail.com
___
Python tracker
<http://bugs.python.org/issue18199>
___
___
Python-bugs-list mailing list
Unsub
Changes by Berker Peksag :
--
nosy: +Aaron.Meurer, Voo, daniel.ugra, eryksun, ezio.melotti, haypo, jens,
loewis, pitrou, santoso.wijaya, serhiy.storchaka, steve.dower, zach.ware
___
Python tracker
<http://bugs.python.org/issue18
Changes by Berker Peksag :
--
Removed message: http://bugs.python.org/msg271888
___
Python tracker
<http://bugs.python.org/issue18199>
___
___
Python-bugs-list m
Berker Peksag added the comment:
I'm going to close this as 'works for me' since there is no way to reproduce
the crash consistently. Also, we don't support Windows XP anymore and sum.v4.py
worked fine for me in Windows 10.
See also http://code.activestate.com/lists/pyt
Changes by Berker Peksag :
--
nosy: +berker.peksag
stage: -> patch review
versions: +Python 3.5, Python 3.6 -Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Berker Peksag added the comment:
> Kernel 2.6.18 is also quite old, so if there is no feedback if this is still
> an issue I'd suggest to close the report.
Agreed. And without more information, there is nothing we can do here.
--
nosy: +berker.peksag
resolution: -> n
Berker Peksag added the comment:
I find pull requests templates more useful:
https://github.com/blog/2111-issue-and-pull-request-templates and we already
have a template to warn users:
https://github.com/python/cpython/blob/master/.github/PULL_REQUEST_TEMPLATE.md
--
nosy
Berker Peksag added the comment:
Sorry, I forgot to share a screenshot in my earlier message:
https://dl.dropboxusercontent.com/u/166024/pr-template.png
--
___
Python tracker
<http://bugs.python.org/issue27
Berker Peksag added the comment:
Which browser do you use? How big is the CSV file? Modern browsers tend to do
aggressive prefetching so this might be the cause here.
--
nosy: +berker.peksag
___
Python tracker
<http://bugs.python.org/issue27
Berker Peksag added the comment:
This is a duplicate of issue 21578.
--
nosy: +berker.peksag
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Misleading error message when ImportError called with invalid
keyword args
type:
Changes by Berker Peksag :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue27697>
___
___
Changes by Berker Peksag :
--
keywords: +easy
stage: -> needs patch
type: -> behavior
versions: +Python 3.5, Python 3.6 -Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/i
Berker Peksag added the comment:
Thanks for the report. This is a duplicate of issue 1104.
--
nosy: +berker.peksag
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Berker Peksag added the comment:
All obvious bugs have already been fixed.
--
nosy: +berker.peksag
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.o
Berker Peksag added the comment:
The imp module has been deprecated long time ago and the importlib module
itself doesn't it anymore. However, Cython still use it:
https://github.com/cython/cython/blob/master/pyximport/pyximport.py#L217
I'm inclined to close this as 'out of
Berker Peksag added the comment:
Thanks for the report.
Most of the csv.Error usages are in Modules/_csv.c. You can search for
"_csvstate_global->error_obj" in the module's source code. I think the
documentation is correct as is.
--
nosy: +berker.peksag
resolut
Berker Peksag added the comment:
Good catch, thanks! I went with Ezio's suggestion but left 2.7 documentation as
is.
--
nosy: +berker.peksag
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
type: enhancement -> behavior
versions: +Pytho
Changes by Berker Peksag :
--
keywords: +easy
stage: -> needs patch
versions: +Python 3.5, Python 3.6 -Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Berker Peksag added the comment:
I've changed the dead code to
assert(d != NULL);
and added the following sentence to PyModule_GetDict documentation:
If *module* is not a module object (or a subtype of a module object),
:exc:`SystemError` is raised and *NULL* is ret
Changes by Berker Peksag :
--
keywords: +easy
stage: -> needs patch
versions: +Python 3.6 -Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Berker Peksag added the comment:
Thanks for the patch, but I prefer keeping the section shorter. Also, note that
disabling verification globally is discouraged in the PEP.
--
nosy: +berker.peksag
resolution: -> rejected
stage: -> resolved
status: open -&g
Berker Peksag added the comment:
Thanks for the report!
The default values of fp and environ parameters are already documented in the
function signature in Python 3:
cgi.parse(fp=None, environ=os.environ, keep_blank_values=False,
strict_parsing=False)
In Python 2, the function signature
2101 - 2200 of 3715 matches
Mail list logo
