Alexander Mohr added the comment:
actually it does show in 3.5.2, it doesn't show when using get_object, but it
does when using head_object, and they both throw the same exception, so weird.
--
___
Python tracker
<https://bugs.py
Alexander Belopolsky added the comment:
Well, even in non-POSIX mode timegm and gmtime are the inverse of one another
in BSD. The problem that you see stems from the fact that time.gmtime is
implemented as a call to the namesake C function while calendar.timegm is
implemented in pure Python
Alexander Mohr added the comment:
here's another problem, if I change that function signature to:
def test(s3_client):
try:
method = getattr(s3_client, sys.argv[1])
method(Bucket='archpi.dabase.com', Key='doesnotexist')
except botocore.ex
Alexander Mohr added the comment:
I believe your method is flawed, when enabling tracemalloc it's going to be
using memory as well to store the traces. I still believe you need to use the
method I mentioned and further even if we don't take into account the total
memory th
Alexander Mohr added the comment:
that's not going to affect
http://pytracemalloc.readthedocs.io/api.html#get_traced_memory. There is no
filter for that :)
as to your sum that's exactly what my original callstack lists:
21 memory blocks: 4.7 KiB
this means 21 blocks were not rel
Alexander Mohr added the comment:
yes, memory does go up. If you click the botocore bug link you'll see a graph
of memory usage over time.
--
___
Python tracker
<https://bugs.python.org/is
Alexander Mohr added the comment:
INADA Naoki: Unfortunately you'll need to use credentials from a free AWS
account: https://aws.amazon.com/free/. Then create a credentials file in
~/.aws/credentials:
https://docs.aws.amazon.com/cli/latest/userguide/cli-config-files
Alexander Mohr added the comment:
I'll try with that fix and see if the leak is fixed, is the reasoning that if
the warning happens after the try/except scope and that's why the callstack has
it?
--
___
Python tracker
<https://bu
Alexander Mohr added the comment:
not fixing this means that 3.6 slowly leaks for many people in prod. It's not
often possible to fix all the warnings on large dynamic applications, I highly
suggest finding a way to get this into 3.6. I bet there are a lot of
frustrated people out
Alexander Mohr added the comment:
Ok I've verified that the patch does indeed fix the leak detected. Thank you
very much INADA for knowing that there was a leak in the warnings module, I
would have never guessed, especially given the tracemalloc stack given. Had it
showed a callstack
Alexander Mohr added the comment:
actually, thinking about this more on my way to work, this should NOT be
closed. The callstack I initially mentioned still has no explanation and we
now know is not correct. It should either have listed something related to
warnings, or nothing at all
Alexander Mohr added the comment:
ok fair enough, however a caveat is that it's not necessarily end of function
as I was able to expand the function by a few more lines and the callstack
stayed the same, however I'm guessing the interpreter was smart enough to
realize the calls bel
Alexander Mohr added the comment:
of course, sorry, I meant in a gender neutral way
--
___
Python tracker
<https://bugs.python.org/issue33565>
___
___
Python-bug
Alexander Mohr added the comment:
this is how my friends talk here, see:
https://english.stackexchange.com/questions/11816/is-guy-gender-neutral
--
___
Python tracker
<https://bugs.python.org/issue33
Change by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<https://bugs.python.org/issue33649>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<https://bugs.python.org/issue33701>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Alexander Belopolsky :
--
stage: -> needs patch
versions: -Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue28602>
___
_
Alexander Belopolsky added the comment:
> it's actually possible to implement full `fold` support in a generic way
I am aware of that. In fact, some of the draft versions of PEP 495
implementation did contain such code. The problem is that any such
tz.fromutc() implementati
Alexander Belopolsky added the comment:
Paul,
In your opening post to this issue you suggested to change one line [1] in
Lib/datetime.py from
dtdst = dt.dst()
to
dtdst = dt.replace(fold=1).dst()
This looks like a rather innocuous change, but it does not by itself make
fromutc() return
New submission from Alexander Belopolsky :
Since implementation of issue 25283, the objects returned by time.localtime
always have tm_zone and tm_gmtoff attributes, but the datetime module still has
code that anticipates these attributes to be missing. [1]
[1]:
https://github.com/python
Change by Alexander Belopolsky :
--
components: -Extension Modules
___
Python tracker
<https://bugs.python.org/issue33810>
___
___
Python-bugs-list mailin
Change by Alexander Belopolsky :
--
keywords: +patch
pull_requests: +7182
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Alexander Belopolsky :
--
pull_requests: +7183
___
Python tracker
<https://bugs.python.org/issue25283>
___
___
Python-bugs-list mailing list
Unsub
Alexander Belopolsky added the comment:
New changeset bcb032e4acdebc043a7659a06e6037fe71020860 by Alexander Belopolsky
in branch 'master':
bpo-33810 Remove unused code from datetime.py. (GH-7549)
https://github.com/python/cpython/commit/bcb032e4acdebc043a7659a06e6037
Alexander Belopolsky added the comment:
New changeset bcb032e4acdebc043a7659a06e6037fe71020860 by Alexander Belopolsky
in branch 'master':
bpo-33810 Remove unused code from datetime.py. (GH-7549)
https://github.com/python/cpython/commit/bcb032e4acdebc043a7659a06e6037
Change by Alexander Belopolsky :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Alexander Belopolsky :
--
nosy: belopolsky
priority: normal
severity: normal
status: open
title: Different behavior betwee
___
Python tracker
<https://bugs.python.org/issue33
New submission from Alexander Belopolsky :
Consider the following code:
$ cat bug.py
import sys
if len(sys.argv) > 1:
sys.modules['_datetime'] = None
from datetime import tzinfo, datetime, timezone
class TZ(tzinfo):
def utcoffset(self, t):
pass
print(datetime(20
Alexander Belopolsky added the comment:
So you are suggesting that my datetime(2000,1,1,tzinfo=TZ()) should behave as a
naive instance, right? Well, this would be a third behavior different from
both current C and Python implementations:
>>> print(datetime(2000,1,1).astimezone(tim
Change by Alexander Belopolsky :
--
assignee: -> belopolsky
components: +Extension Modules, Library (Lib)
stage: -> needs patch
type: -> behavior
versions: +Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.or
Change by Alexander Belopolsky :
--
keywords: +patch
pull_requests: +7202
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Alexander Belopolsky added the comment:
Tim, given that I've updated the documentation, should we treat this as a bug
fix or a feature? Note that the type check is definitely a bug-fix (if not a
security issue), but I clearly had a wrong definition of "naive" in mind when I
Change by Alexander Belopolsky :
--
stage: patch review -> commit review
versions: +Python 3.6
___
Python tracker
<https://bugs.python.org/issue33812>
___
_
Alexander Belopolsky added the comment:
New changeset 877b23202b7e7d4f57b58504fd0eb886e8c0b377 by Alexander Belopolsky
in branch 'master':
bpo-33812: Corrected astimezone for naive datetimes. (GH-7578)
https://github.com/python/cpython/commit/877b23202b7e7d4f57b58504fd0eb8
Alexander Belopolsky added the comment:
New changeset 037e9125527d4a55af566f161c96a61b3c3fd998 by Alexander Belopolsky
(Miss Islington (bot)) in branch '3.7':
bpo-33812: Corrected astimezone for naive datetimes. (GH-7578) (GH-7600)
https://github.com/python/cpyt
Alexander Belopolsky added the comment:
New changeset 1d4089b5d208ae6f0bd256304fd77f04c0b4fd41 by Alexander Belopolsky
(Miss Islington (bot)) in branch '3.6':
bpo-33812: Corrected astimezone for naive datetimes. (GH-7578) (GH-7601)
https://github.com/python/cpyt
Change by Alexander Belopolsky :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from Alexander Belopolsky :
Consider the following code:
import sys
def trace(frame, event, arg):
pass
def f():
f()
sys.settrace(trace)
print(sys.gettrace())
try:
f()
except RuntimeError:
pass
print(sys.gettrace())
When I run it, I get
None
Apparently, the
Alexander Belopolsky added the comment:
It looks like this has been known for quite some time. See issue10933.
--
___
Python tracker
<https://bugs.python.org/issue33
Change by Alexander Belopolsky :
--
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue33849>
___
___
Change by Alexander Belopolsky :
--
resolution: -> duplicate
superseder: -> Tracing disabled when a recursion error is triggered (even if
properly handled)
___
Python tracker
<https://bugs.python.org/i
Alexander Belopolsky added the comment:
New changeset 5b6e49a1393b3e2313471696e3568e26296137b4 by Alexander Belopolsky
(Farhaan Bukhsh) in branch 'master':
bpo-30516: Fix documentation issue with -timedelta in datetime (GH-7348)
https://github.com/python/cpyt
Alexander Belopolsky added the comment:
New changeset 55f39bdabc91b387c18451c78ee077e6d05d6cfe by Alexander Belopolsky
(Miss Islington (bot)) in branch '3.6':
bpo-30516: Fix documentation issue with -timedelta in datetime (GH-7348)
(GH-8092)
https://github.com/python/cpyt
Alexander Belopolsky added the comment:
New changeset a8bb18bbb9c286cfac5a0b8c8679c440e5c49305 by Alexander Belopolsky
(Miss Islington (bot)) in branch '3.7':
bpo-30516: Fix documentation issue with -timedelta in datetime (GH-7348)
(GH-8093)
https://github.com/python/cpyt
Change by Alexander Belopolsky :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<https://bugs.python.org/issue34008>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
Unfortunately, the PEP authors did very little in terms of implementing the PEP
and neither CPython nor numpy has a fully compliant implementation.
--
nosy: +aerojockey, teoliphant
___
Python tracker
<ht
Change by Alexander Belopolsky :
--
assignee: -> belopolsky
___
Python tracker
<https://bugs.python.org/issue32780>
___
___
Python-bugs-list mailing list
Un
Alexander Mohr added the comment:
we're compiling similar to debian and getting the same issues now only with 3.7
so interested in what the resolution is. I tried both w/ and w/o setting
SOURCE_DATE_EPOCH and still get failures.
--
nosy: +theh
New submission from Alexander Marshalov <_...@marshalov.org>:
I was faced with the fact that the behavior of the functions "min"/"max" and
"sorted" is a little different.
For example, this code works fine:
>>> sorted([3, 2, 1], key=None)
Change by Alexander Marshalov <_...@marshalov.org>:
--
keywords: +patch
pull_requests: +7864
stage: -> patch review
___
Python tracker
<https://bugs.python.or
New submission from Alexander Marshalov <_...@marshalov.org>:
I would like to make three small improvements to the "heapq" module.
1) The "nsmallest" function has the following code (a similar code exists in
the "nlargest" function):
# When n>=si
Change by Alexander Marshalov <_...@marshalov.org>:
--
keywords: +patch
pull_requests: +7965
stage: -> patch review
___
Python tracker
<https://bugs.python.or
Change by Alexander Marshalov <_...@marshalov.org>:
--
title: Small improvements in heapq (refatoring) -> Small improvements in heapq
(refactoring)
___
Python tracker
<https://bugs.python.or
Alexander Belopolsky added the comment:
New changeset 96d1e69a12ed8ab80203277e1abdaf573457a964 by Alexander Belopolsky
(Ammar Askar) in branch 'master':
bpo-29097: Forego fold detection on windows for low timestamp values (GH-2385)
https://github.com/python/cpyt
Alexander Belopolsky added the comment:
New changeset 973649342cee3869409f341ff0f0e3d2b1547c2a by Alexander Belopolsky
(Miss Islington (bot)) in branch '3.7':
bpo-29097: Forego fold detection on windows for low timestamp values (GH-2385)
(GH-8466)
https://github.com/python/cpyt
Alexander Belopolsky added the comment:
New changeset 6ea8a3a0ebf840ca57b6dba9cad26fbb0ddaa5d4 by Alexander Belopolsky
(Ammar Askar) in branch '3.6':
[3.6] bpo-29097: Forego fold detection on windows for low timestamp values
(GH-2385) (GH-8498)
https://github.com/python/cpyt
New submission from Alexander Tsvetkov :
If more than one thread is waiting for the multiprocessing.pool.AsyncResult
(aka ApplyResult) returned from apply_async, only one thread will be notified
once the result arrives.
It happens because AsyncResult._set calls notify upon the result arrival
Change by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<https://bugs.python.org/issue30140>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Alexander Mohr :
I've been trying to track down a leak in aiohttp:
https://github.com/aio-libs/aiohttp/issues/3010
it seems like this leak now occurs with raw asyncio SSL sockets.
when the gist script is run like so: python3.7 `which mprof` run --interval=1
Alexander Mohr added the comment:
sorry, by "raw" I mean in the context of aiohttp, so just using the normal
python ssl context and asyncio sockets. I don't think it's an object not
getting GC'd because I didn't see any increase on object counts, nor leaks p
Alexander Belopolsky added the comment:
New changeset 92878829c31ab2fc71c60555ce87a5f6cbc876f0 by Alexander Belopolsky
(Christophe Nanteuil) in branch 'master':
bpo-34158: Documentation UTC offset update (GH-8377)
https://github.com/python/cpyt
New submission from Alexander Böhn :
When creating a new type with `typing.NewType(…)` the result is a function
defined on-the-fly with no reasonable `__repr__` definition – the string
representation of the type looks something like e.g. “.new_type at 0x108ae6950>” which isn’t very useful
Change by Alexander Böhn :
--
keywords: +patch
pull_requests: +9187
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34963>
___
___
Py
Change by Alexander Böhn :
--
components: +Library (Lib) -Extension Modules
___
Python tracker
<https://bugs.python.org/issue34963>
___
___
Python-bugs-list mailin
Change by Alexander Böhn :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue34963>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Alexander Böhn :
--
nosy: +levkivskyi
___
Python tracker
<https://bugs.python.org/issue34963>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Böhn added the comment:
The proposed solution in the PR replaces the identity-function return value of
`NewType(…)` with a callable class instance that adds an explicit `__repr__`
function – which that function cobbles together the string representations of
the supplied type and
Alexander Belopolsky added the comment:
It looks like this issue has been fixed by GH-9288. Can this be closed?
Should we backport?
--
___
Python tracker
<https://bugs.python.org/issue34
Alexander Belopolsky added the comment:
I think strptime should only accept %Z when it comes together with %z and not
do any validation.
This is close to the current behavior. %Z by itself is useless because even
when it is accepted, the value is discarded:
>>> print(datetime
Alexander Belopolsky added the comment:
Since the Python datetime only supports dates within 0001-01-01 through
-12-31 range, it is not clear how we can meaningfully support the AD/BC era
designation.
Looking at man strftime page on my Mac, I see that they use every upper an
lower case
Change by Alexander Belopolsky :
--
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Alexander Belopolsky :
--
superseder: -> %Z in strptime doesn't match EST and others
___
Python tracker
<https://bugs.python.org/issue33940>
___
Alexander Belopolsky added the comment:
+1
I had "tsort" in my own utilities library for so long that I thought it was in
stdlib already. I found this issue after unsuccessfully searching
docs.python.org. :-)
I think functools will be a fine place for it. It is somewhat relate
Alexander Belopolsky added the comment:
I left a few minor comments on rietveld for the last patch. I did not see code
for time.now() and I don't think adding now() should be combined with time +/-
timedelta patch. Let's do one thing at a time.
I think time + timedelta addition
Alexander Belopolsky added the comment:
This was proposed before and rejected in issue1118748, but I think current
proposal addresses the ambiguity that was sited as a reason for rejection.
--
nosy: +skip.montanaro
___
Python tracker
<h
Alexander Belopolsky added the comment:
See also issue 3250. If we add mod 24h arithmetics, I would like to see
something like time.add_with_carry(timedelta) -> (int, time) method. With it,
users who need a specific overflow behavior will be able to implement it easily:
def check_add(t,
Alexander Belopolsky added the comment:
I am changing the title to focus this issue on arithmetics. Lack of time.now()
is adressed in #8902.
--
title: datetime.time support for '+' and 'now' -> datetime.time support for '+'
and '-'
___
Changes by Alexander Belopolsky :
--
resolution: wont fix ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue8902>
___
___
Pyth
Changes by Alexander Belopolsky :
--
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue8902>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
This is not a bug in datetime.timezone. The value returned by
timezone.tzname() is documented and the code works correctly. %Z should not be
used to produce machine-readable timestamps and for a human reader
'UTC+03:00+0300' should not be
Alexander Belopolsky added the comment:
Python 2.x is in maintenance mode and will not receive new features. In 3.x
this is already implemented:
Python 3.3.2 (default, May 24 2013, 22:46:58)
[GCC 4.2.1 Compatible Apple LLVM 4.2 (clang-425.0.28)] on darwin
Type "help", "copyr
Alexander Belopolsky added the comment:
I am changing the title slightly to include '\N{MINUS SIGN}' in the scope of
this issues. See [1]:
"Unless anyone can point me to a case where \N{MINUS SIGN} should not be
treated as a (duh) minus sign, we should go and try to make life
New submission from Alexander Belopolsky:
Reference to
http://www.unicode.org/Public/6.0.0/ucd/extracted/DerivedNumericType.txt in
http://docs.python.org/3.4/library/stdtypes.html#numeric-types-int-float-complex
should be changed to
http://www.unicode.org/Public/6.1.0/ucd/extracted
Alexander Belopolsky added the comment:
As a design principle, "accept what's unambiguous in any locale" is reasonable,
but it is hard to apply consistently. I would agree that the status quo is
hard to defend. After a long discussion, it has been accepted that fullwidth
d
Alexander Belopolsky added the comment:
I don't have a system affected by the change, but the explanation and the patch
look right to me.
FWIW, the patch applies cleanly to 3.4 head and passes 'make test'.
--
stage: -> commit review
versions: +Pyth
Changes by Alexander Belopolsky :
--
hgrepos: +197
___
Python tracker
<http://bugs.python.org/issue18176>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexander Belopolsky :
--
keywords: +patch
Added file: http://bugs.python.org/file30531/686836ad3042.diff
___
Python tracker
<http://bugs.python.org/issue18
Alexander Belopolsky added the comment:
This is a trivial change, but I would like someone to review this in case there
is a better solution to keep this in sync with unicodedata.unidata_version.
--
assignee: -> docs@python
keywords: +needs review
nosy: +docs@python
stage: ->
Alexander Belopolsky added the comment:
The latest patch at #2382 is simpler than mine, so I am closing this as
duplicate.
--
resolution: -> duplicate
status: open -> closed
superseder: -> [Py3k] SyntaxError cursor shifted if multibyte character is
Alexander Belopolsky added the comment:
haypo> The purpose of this issue is to handle CJK characters taking 2 haypo>
columns instead of 1 in a terminal, or did I misunderstand it?
That's the other half of the problem, but the more common issue is misplaced
caret when non-ascii cha
Alexander Belopolsky added the comment:
Serhiy's patch is lacking tests, but it passes the test I proposed at #10382 at
attaching here.
--
Added file: http://bugs.python.org/file30534/test.py
___
Python tracker
<http://bugs.python.org/i
Alexander Belopolsky added the comment:
This is essentially a duplicate of #10581, so I am closing this and will
summarize the situation there.
--
resolution: -> duplicate
status: open -> closed
superseder: -> Review and document string format accepted in numeric
Alexander Belopolsky added the comment:
It looks like we a approaching consensus on some points:
1. Mixed script numerals should be disallowed.
2. '\N{MINUS SIGN}' should be accepted as an alternative to '\N{HYPHEN-MINUS}'
Open question: should we accept fullwidth + an
Alexander Belopolsky added the comment:
PEP 393 implementation has already added the fast path to decimal encoding:
http://hg.python.org/cpython/diff/8beaa9a37387/Objects/unicodeobject.c#l1.3735
What we can do, however, is improve performance of converting non-ascii
numerals by looking up
Changes by Alexander Belopolsky :
Added file: http://bugs.python.org/file30608/bd092995907c.diff
___
Python tracker
<http://bugs.python.org/issue18176>
___
___
Python-bug
Alexander Belopolsky added the comment:
Here is what grep revealed:
$ find Doc -name \*.rst | xargs grep -n '6\.2\.0'
Doc/library/stdtypes.rst:357: See
http://www.unicode.org/Public/6.2.0/ucd/extracted/DerivedNumericType.txt
Doc/library/unicodedata.rst:18:this database is compile
New submission from Alexander Belopolsky:
At the minimum, we should refer to unicode.org:
http://www.unicode.org/versions/Unicode6.1.0/#Database_Changes (for Python 3.3),
http://www.unicode.org/versions/Unicode6.2.0/#Database_Changes (for Python 3.4).
We may also want to highlight changes that
Alexander Belopolsky added the comment:
Here is another change that I think deserves an explicit mention in "What's
New":
Python 3.3.2
>>> exec('a\u17B4 = 5')
>>> eval('a\u17B4')
5
Python 3.2.5
>>> exec('a\u17B4 = 5')
Tra
Alexander Belopolsky added the comment:
I have found another place where explicit UCD version is used in the docs:
Doc/reference/lexical_analysis.rst:729:.. [#]
http://www.unicode.org/Public/6.1.0/ucd/NameAliases.txt
I am not sure how this case should be handled. The language reference was
2001 - 2100 of 4096 matches
Mail list logo
