Change by Karthikeyan Singaravelan :
--
pull_requests: +7358
___
Python tracker
<https://bugs.python.org/issue33859>
___
___
Python-bugs-list mailing list
Unsub
Karthikeyan Singaravelan added the comment:
There are certain encodings as I went through the file Lib/encodings/aliases.py
where there are all digit items that doesn't correspond to cp sequence. I
think the search function is used not only for encodings that start with 'cp'
and thus
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue33830>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Thanks much @rhettinger and the team for all the work on documentation. This is
my first patch and I am pretty amazed at the smooth experience for a beginner
like me with GitHub and helpful bots. I hope to contribute more.
Just wanted to leave
Karthikeyan Singaravelan added the comment:
Thanks @serhiy.storchaka . I looked into the code and it seems the resolution
is done in `search_function` at Lib/encodings/__init__.py . It seems that
encoding is normalized using some logic and then we use the normalized encoding
to check
Karthikeyan Singaravelan added the comment:
I am able to verify the newly added aliases using the below assert statement
assert codecs.encode('a', '874') == codecs.encode('a', 'cp874')
I am struck on the part where it could be patched in the search_function and I
hope this is the approach
New submission from Karthikeyan Singaravelan :
I have found some typos in docs folder using aspell. I have fixed them. The
changes are as below :
Doc/library/codecs.rst - cypher - cipher
Doc/library/email.rst - Protcol - Protocol
Doc/library/importlib.rst - abstact - abstract
Doc/library
Change by Karthikeyan Singaravelan :
--
keywords: +patch
pull_requests: +7304
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Karthikeyan Singaravelan added the comment:
Interesting. I googled this and came across this note which covers this :
https://docs.python.org/2/faq/programming.html#why-does-a-tuple-i-item-raise-an-exception-when-the-addition-works
--
nosy: +xtreak
Karthikeyan Singaravelan added the comment:
Congratulations! All the changes and patches are collected in Misc/NEWS.d file.
You can find more information and the process to create one here :
https://devguide.python.org/committing/?highlight=blurb#what-s-new-and-news-entries
.
Happy hacking
Karthikeyan Singaravelan added the comment:
I was making a patch for this and both Python 2.7 and Python 3.6 returned "404
OK" for the example instead of "404 Not Found". I think the end-point is
misleading and it's better to use httpbin.org for this.
cpython git:(maste
Change by Karthikeyan Singaravelan :
--
keywords: +patch
pull_requests: +7386
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Karthikeyan Singaravelan added the comment:
I think if we can get a confirmation from @Prawin that adding an alias fixed
the issue or a minimal test case then it will be helpful. The minimal I can
come up with is as below :
import codecs
# Fails without alias being added other cases like
Karthikeyan Singaravelan added the comment:
I have added the aliases as per comment by @vstinner
https://bugs.python.org/msg319590 . I have used
https://docs.python.org/3.8/library/codecs.html#standard-encodings as a
reference to see if there are any additional aliases to add with respect
Change by Karthikeyan Singaravelan :
--
keywords: +patch
pull_requests: +7321
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Karthikeyan Singaravelan added the comment:
Thanks @ronaldoussoren for the links. I have added an entry using blurb tool
and updated the docs at Doc/library/codecs.rst with relevant aliases.
Thanks
--
___
Python tracker
<https://bugs.python.
Karthikeyan Singaravelan added the comment:
I tried the test case on master branch. I ran the test case on 1GB RAM Linux
based digitalocean droplet to have the script killed. Please find the results
as below :
# Python build
➜ cpython git:(master) ✗ ./python
Python 3.8.0a0 (heads/bpo33095
Karthikeyan Singaravelan added the comment:
@r.david.murray I googled the error message and I hope you are referring to the
below issue which has a patch and test.
issue : https://bugs.python.org/issue32498
--
nosy: +xtreak
___
Python tracker
Karthikeyan Singaravelan added the comment:
There are four parts where I could see sys.path manipulation being mentioned
while running scripts :
-c option (https://docs.python.org/3/using/cmdline.html#cmdoption-c)
-m option (https://docs.python.org/3/using/cmdline.html#cmdoption-m
Karthikeyan Singaravelan added the comment:
This is tracked at https://github.com/python/pythondotorg/issues/1252
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue33
Karthikeyan Singaravelan added the comment:
@stein-k Thanks for the patch and tests. The patches apply cleanly on master
branch. The project accepts pull requests and it will be helpful if you can
make a PR for this on GitHub to get this merged. Since this is a bug fix I
think it would
Karthikeyan Singaravelan added the comment:
Thanks for the issue. I think this is documented here :
https://docs.python.org/3/library/unittest.mock-examples.html#coping-with-mutable-arguments
Thanks
--
nosy: +xtreak
___
Python tracker
<ht
Change by Karthikeyan Singaravelan :
--
pull_requests: +7372
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issue33095>
___
_
Karthikeyan Singaravelan added the comment:
Thanks for the report. I think it's a false positive and the md5 you have
attached matches with the official release of 2.7.14 installer that you can
verify from https://www.python.org/downloads/release/python-2714/. There were
similar cases
Karthikeyan Singaravelan added the comment:
Okay, got it. Sorry for the noise. Closing it.
Thanks
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Karthikeyan Singaravelan added the comment:
Related issue that introduced the error message if you would like to take a
look at the implementation : https://bugs.python.org/issue30597
Thanks
--
nosy: +xtreak
___
Python tracker
<ht
Karthikeyan Singaravelan added the comment:
I took an initial stab at this and there is a comment where if there is an open
paren then to use the normal error message. Additional context on the issue
which lists false positive cases where the change was introduced
https://bugs.python.org
Change by Karthikeyan Singaravelan :
--
pull_requests: +7654
___
Python tracker
<https://bugs.python.org/issue33978>
___
___
Python-bugs-list mailing list
Unsub
Karthikeyan Singaravelan added the comment:
@corona10 You might want to discuss this at
https://mail.python.org/pipermail/python-ideas/ so that you get some initial
feedback on the work and it's acceptance to the core.
Thanks
--
___
Python
Karthikeyan Singaravelan added the comment:
Thanks much @maggyero for the original report and sample test case this was my
first non-easy bug fix. Thanks @vinay.sajip for the guidance on logging module
implementation.
Thanks
--
versions: -Python 3.7, Python 3.8
Karthikeyan Singaravelan added the comment:
I think it's a problem with user-level permission error not being able to
create a process (Wild guess to try sudo?). The tests run without error for me.
Please add in information regarding you environment, gdb version and perhaps
the whole output
Karthikeyan Singaravelan added the comment:
It failed for the first time on Ubuntu and then was successful for all the rest
of 5-6 runs. I don't know why for the failure run it has load avg as 0.00 and
how to get to this stage.
# Shell session
➜ cpython git:(master) uname -a
Linux ubuntu-s
New submission from Karthikeyan Singaravelan :
I was checking on https://bugs.python.org/issue30345 and
https://bugs.python.org/issue33914. I looked into Travis and VSTS builds for
test_gdb. Though python is built with `--with-pydebug` gdb is not installed in
the builds and hence
New submission from Karthikeyan Singaravelan :
There was a change made in collections.Counter that made it accept self as the
first parameter and hence while doing *args in the method signature args[0] is
always set as the self. Hence the check for `not args` becomes a no-op during
Karthikeyan Singaravelan added the comment:
Thanks @prawin for the confirmation. There is a mailing list discussion at
https://groups.google.com/forum/#!topic/python-ideas/Ny1RN9wY0cI and it seems
this is related to Thai language locale. Feel free to add in if you have any
more input
New submission from Karthikeyan Singaravelan :
Python 3 supports type annotations in functions but when there is a TypeError
due to calling a function then only the arguments are given in the error
message. If the function has type annotations then adding them to the error
message will give
Karthikeyan Singaravelan added the comment:
Upstream issue was resolved : https://github.com/pypa/setuptools/issues/1394
Thanks
--
status: pending -> open
___
Python tracker
<https://bugs.python.org/issu
Change by Karthikeyan Singaravelan :
--
keywords: +patch
pull_requests: +8148
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Karthikeyan Singaravelan added the comment:
Related issue : https://bugs.python.org/issue34326
Thanks
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34
Karthikeyan Singaravelan added the comment:
Some of VSTS Mac OS and Linux builds also have the same failure
Sample Linux :
https://python.visualstudio.com/cpython/_build/results?buildId=21154=logs
Sample Mac OS :
https://python.visualstudio.com/cpython/_build/results?buildId=21155=logs
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34325>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Ah sorry, I don't know why it opened this bug while adding a comment. Feel free
to change the status.
Thanks
--
___
Python tracker
<https://bugs.python.org/issue34
Karthikeyan Singaravelan added the comment:
I tried the tests on FreeBSD 11.x and FreeBSD 10.x digitalocean droplets with
master branch and the tests pass. Adding information that might be helpful.
# FreeBSD 11.2-RELEASE
root@freebsd-s-1vcpu-1gb-blr1-01:~/cpython # uname -a
FreeBSD freebsd-s
Karthikeyan Singaravelan added the comment:
This is an issue with Python 2 too which I hope can be fixed too. The original
logic in the code was committed around 16 years back :
https://github.com/python/cpython/commit/bbc0568a5c7d3849a22c78d545823a4b952c0933
and tests are also around 10
Karthikeyan Singaravelan added the comment:
I just checked back the behavior on Perl's https://github.com/libwww-perl/URI/
. It seems to handle that along with other additional cases. Maybe some of the
tests can be adopted from there for better coverage too
(https://github.com/libwww-perl
Karthikeyan Singaravelan added the comment:
I have added support for functions defined inside a function and methods of a
class along with some basic tests. Since directly taking co_name from code
object returns only the name without any context like Foo.square inside square
when I try
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34272>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34269>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Not reproducible in latest 3.7 branch. Search for "django segmentation fault"
returns me https://bugs.python.org/issue34087 which is also unicode related and
contains a django test project . I hope the related ticket is the one. F
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34241>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Interesting. It works fine with Python 3.6 and latest master but segfaults in
python 3.7.0 . I will try the latest python 3.7 branch later.
# Python 3.6 on Mac
(bpo34241-env)mysite git:(master) python
Python 3.6.4 (default, Mar 12 2018, 13:42
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34229>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Is there a way to test this or trigger this code using Python syntax?
`slice(start, stop, step).indices()` uses slice_indices in
Objects/sliceobject.c . I checked the function docs
https://docs.python.org/2.7/c-api/slice.html#c.PySlice_GetIndices
Karthikeyan Singaravelan added the comment:
Seems like this is the same as https://bugs.python.org/issue30156.
Relevant commit :
https://github.com/python/cpython/commit/7822f151b68e40376af657d267ff774439d9adb9
.
Comment on the commit :
https://github.com/python/cpython/commit
Karthikeyan Singaravelan added the comment:
Can reproduce this on Python 3.5 and 3.6 too
# Python 3.5
➜ cpython git:(f497e74) $ ./python
Python 3.5.6rc1+ (remotes/upstream/3.5:f497e74, Jul 25 2018, 14:32:33)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", &
Karthikeyan Singaravelan added the comment:
Python 3.4 seems fine
➜ cpython git:(57b85d3) ./python
Python 3.4.9rc1+ (default, Jul 25 2018, 14:39:07)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more informa
Karthikeyan Singaravelan added the comment:
Seems related : https://bugs.python.org/issue31121
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue33
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34226>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
On a similar note SpooledTemporaryFile is also documented as a function though
it's a class. Ref :
https://docs.python.org/3.8/library/tempfile.html#tempfile.SpooledTemporaryFile
--
nosy: +xtreak
Karthikeyan Singaravelan added the comment:
I was just searching for the line and came to know it's a Monty Python
reference :) There seems to be a similar example here with reference to this :
https://docs.python.org/3.8/library/tarfile.html#command-line-interface
python -m tarfile -c
Karthikeyan Singaravelan added the comment:
I think I have found the bug. When we call setLevel then to clear the cache
value of Logger objects `logging.Logger.manager.loggerDict.values()`
(https://github.com/python/cpython/blob/9c18b1ae527346bc178250ad1ca07bffdacde5dd/Lib/logging/__init__
Change by Karthikeyan Singaravelan :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue34269>
___
___
Python-bugs-list mailing list
Unsub
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue31506>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34203>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Okay, I did some code search on GitHub for
`logging.Logger.manager.loggerDict.clear()`
(https://github.com/search?q=logging.Logger.manager.loggerDict.clear%28%29=Code)
and there was some code in the test_logging where it was used in tearDown
Karthikeyan Singaravelan added the comment:
➜ cpython git:(70d56fb525) ✗ ./python.exe
Python 3.7.0a2+ (tags/v3.7.0a2-341-g70d56fb525:70d56fb525, Jul 31 2018,
21:58:10)
[Clang 7.0.2 (clang-700.1.81)] on darwin
Type "help", "copyright", "credits" or
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34294>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34304>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34303>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
The reported behavior is reproducible in master as well as of ea68d83933 but
not on 3.6.0. I couldn't bisect to the exact commit between 3.7.0 and 3.6.0
where this change was introduced though. I can also see some deprecation
warnings as below
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34330>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue33954>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
I think this is an explicit decision to remove it in Python 3 unless I am
mistaking the syntax you are referring to. Please refer :
https://www.python.org/dev/peps/pep-3113/ . A note on 2to3 to fix this :
https://www.python.org/dev/peps/pep-3113
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34315>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34319>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
keywords: +patch
pull_requests: +8003
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
New submission from Karthikeyan Singaravelan :
Test6012 is not run as part of make test since it's not added to
support.run_unittest at the end of the file. Hence running the test as a single
file causes error. It seems argparsing related test which is a part of
_testcapi.module.c in Python 3
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34276>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
The assertion also fails on master. I did some manual git blame work. The
assertion passes with commit 7324b5ce8e7c031a0a3832a6a8d7c639111ae0ff. It fails
with the next commit 078f1814f1a4413a2a0fdb8cf4490ee0fc98ef34
(https://bugs.python.org
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue27794>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34220>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Seems related : https://bugs.python.org/issue15317
Thanks
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34
Karthikeyan Singaravelan added the comment:
I took all the commits made to Lib/email from 3.5 to latest of 3.6 branch with
`git log --oneline --format="%h" upstream/3.5..upstream/3.6 Lib/email >
commits.txt`
I could see the test fails with a87ba60 and passes with d94ef8f. Probab
Karthikeyan Singaravelan added the comment:
Thanks for the feedback on this. Brett also gave feedback on the python-ideas
mailing list as below :
> Two things to quickly mention: one is that type hints have no run-time
> semantics, so adding them to such a critical exception
Karthikeyan Singaravelan added the comment:
It seems there was a major refactor in traceback module with
6bc2c1e7ebf359224e5e547f58ffc2c42cb36a39 where this was fixed in Python 3.
Ignoring the KeyError seems reasonable to me.
Thanks
--
nosy: +xtreak
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34360>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34367>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
Thanks for the script. I can reproduce this on master and Python 3.6 too.
Sometimes the attached script causes timeout error. Running it under gdb gives
me below :
[New Thread 0x18ab of process 10682]
[New Thread 0x1903 of process 10682]
[New
Karthikeyan Singaravelan added the comment:
Adding Vinay for his thoughts on this. Also Python 3.4 and 3.5 are in security
fixes only mode and can be removed.
Thanks
--
nosy: +vinay.sajip, xtreak
___
Python tracker
<https://bugs.python.
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34349>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
I think this can be closed with
https://github.com/python/buildmaster-config/commit/9a456462fb891328b5b8a170522d5f56f480fdfb.
The buildbots are also green now with the failure reported in
https://buildbot.python.org/all/#/builders/147/builds/174
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34369>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34358>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
I can also reproduce the original script's segfault in 2.7 but not in master.
There is a related bug as per the original description by Dmitry that
itertools.tee is not thread safe in https://bugs.python.org/msg323817 and a
related SO answer
Karthikeyan Singaravelan added the comment:
This might be redundant but I googled 'itertools tee thread safe' and came
across a detailed SO answer from 2017 that explains the issue along with a
similar example that causes segfault in the compiler but it was not reported
here it seems
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34535>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue22872>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Karthikeyan Singaravelan :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue34334>
___
___
Python-bugs-list mailing list
Unsubscribe:
Karthikeyan Singaravelan added the comment:
@prudvinit
Reference :
https://docs.python.org/3.8/library/unittest.html#unittest.TestCase.maxDiff
> This attribute controls the maximum length of diffs output by assert methods
> that report diffs on failure. It defaults to 80*8 char
Karthikeyan Singaravelan added the comment:
@victor I am little confused over the issue since you have said
"`assertDictEqual()` "will be used by default to compare dictionaries in calls
to assertEqual()" and "`maxDiff` doesn't apply to `assertEqual()` when
comparing d
1 - 100 of 3093 matches
Mail list logo