Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Hmm, apparently inspect was made to work with zipped modules back in r45248 .
I cannot reproduce the problem either.
Jean-Paul, can you attach your foobar.zip? What else do you have in your
/tmp dir
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Thanks, Jean-Paul, I can now reproduce your problem and I think I found
the culprit.
I believe the file name check in linecache.updatecache is unnecessary
and is responsible for this problem. With the following patch:
-
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4216>
___
_
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4220>
___
_
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Mark,
I noticed that you replaced a call to _PyLong_AsScaledDouble with your
round to nearest algorithm. I wonder if _PyLong_AsScaledDouble itself
would benefit from your change. Currently it is used in PyLong_AsDoubl
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
I am not sure whether it is appropriate to comment on a closed issue,
but if the tracker will take this comment, hopefully it will find the
right audience.
I have recently stumbled on this bug running python 2.5. While trackin
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
amaury> What if PyGC_Collect() is called just before?
That would work. With the following patch:
===
--- Python/import.c (revision 67183)
+++ Python
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
versions: +Python 2.5.3, Python 2.6, Python 2.7
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Chris> I keep needing to know the number of seconds that a timedelta
Chris> represents.
I propose an alternative approach that I believe will neatly solve
fractional vs. whole seconds and multitude of conceivable toxxx met
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4111>
___
_
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
The patch no longer applies to trunk, but that would be trivial to fix.
Changes like these have been accepted with little resistance in the past
(see e.g. issue651362), so I don't see why this patch has been pending
f
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
The new patch looks fine to me. It applies and compiles without
warnings and the changes are now reflected in the docs. I guess
someone would need to write a NEWS entry because it is a public API
change, but otherwise I would
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +jhylton
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1699259>
___
_
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
While technically this is an API change, in reality it is unlikely to
break anyone's code because you can always pass char * to a function
that expects const char* and the ABI does not change. (Also I cannot
think why a
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
I was going to say the same as Amaury: timedelta / timedelta is
dimensionless (time units cancel each other in division) and the
advantage of this notation is that you get a way to express
timedelta.toxxx for all units accep
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
I attaching webograph's patch updated to revision 67223 where I added a
few tests.
I am +1 on the floor divide changes (allowing timedelta // timedelta),
but I am not sure how true division should work if at all. For t
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +amaury.forgeotdarc, jribbens
versions: +Python 2.7, Python 3.1
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Fri, Nov 14, 2008 at 12:51 PM, STINNER Victor <[EMAIL PROTECTED]> wrote:
>
> STINNER Victor <[EMAIL PROTECTED]> added the comment:
>
> Why not also implementing divmod()? It's useful to split a ti
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Also, why not
>>> divmod(timedelta(3), 2)
(datetime.timedelta(1), datetime.timedelta(1))
?
And where do we stop? :-)
On Fri, Nov 14, 2008 at 1:02 PM, Alexander Belopolsky
<[EMAIL PROTECTED]> wrote:
> On Fri,
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
While I agree that divmod may be useful, your particular use case is
not convincing. The same can be done easier without divmod:
def formatTimedelta(delta):
return "{0}h {1}min {2}sec".format(*str(delta).split(&
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Fri, Nov 14, 2008 at 1:28 PM, STINNER Victor <[EMAIL PROTECTED]> wrote:
..
> What do you think about:
> timedelta / # only with __future__.divison
> timedelta //
> timedelta %
> divmod(timedelta, )
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Oops, the tracker ate some lines from e-mail. Reposting through the
web:
On Fri, Nov 14, 2008 at 1:28 PM, STINNER Victor <[EMAIL PROTECTED]>
wrote:
..
> What do you think about:
> timedelta / # only with
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
haypo> How? I don't understand your suggestion.
Sorry, another case of mail to tracker bug. Here is what I wrote:
"""
.. you can convert delta to time using an arbitrary anchor date and
extract hms that
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
I would like to voice my opposition the totimestamp method.
Representing time as a float is a really bad idea (originated at
Microsoft as I have heard). In addition to the usual numeric problems
when dealing with the floating
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Fri, Nov 14, 2008 at 8:37 PM, STINNER Victor <[EMAIL PROTECTED]> wrote:
> .. but we can create new methods like:
> datetime.fromepoch(seconds, microseconds=0)# (int/long, int)
While 1970 is the most popula
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Sat, Nov 15, 2008 at 5:08 AM, Mark Dickinson <[EMAIL PROTECTED]> wrote:
>
> Mark Dickinson <[EMAIL PROTECTED]> added the comment:
>
>> timedelta / should be disallowed in true division mode.
>
&g
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
@Christian
Adding a __float__ method to datetime was entertained back in 2003, but
was rejected. The same reasons apply to timedelta:
"""
- A C double doesn't have enough precision for roundtrip guarantees.
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Mon, Nov 24, 2008 at 9:04 AM, David Fraser <[EMAIL PROTECTED]> wrote:
...
> The point for me is that having to interact with Microsoft systems that
> require times means that the conversions have to be done.
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
That's an impressive summary, but what is your conclusion? I don't
see any format that will benefit from a subsecond
timedelta.totimestamp(). Your examples have either multisecond or
submicrosecond resolution.
On Mon,
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Mon, Nov 24, 2008 at 12:13 PM, STINNER Victor <[EMAIL PROTECTED]> wrote:
..
> Hum, it's maybe not possible to choose between integer and float. Why
> not supporting both? Example:
> - totimestamp()-&
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Mon, Nov 24, 2008 at 12:34 PM, STINNER Victor <[EMAIL PROTECTED]> wrote:
..
>> I would still prefer totimestamp()->(int, int) returning (sec, usec)
>> tuple. The important benefit is that such toti
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4335>
___
_
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4331>
___
_
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
No, I only used __main__.py to make it easy to reproduce the problem.
Pdb will not be able to access code in any module with a custom
__loader__. For example, if you move f() to foo.py inside test.zip
and import it from __main_
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Off-topic: How to report a bug tracker bug?
The e-mail I sent in response to Nick's post started with:
"""
On Wed, Dec 3, 2008 at 3:51 PM, Nick Coghlan <[EMAIL PROTECTED]>
wrote:
> Just to confir
New submission from Alexander Belopolsky <[EMAIL PROTECTED]>:
>From issue4197:
"""
runpy needs a non-standard PEP 302 extension to set __file__ correctly
in the modules it runs. The pkgutil stuff it uses to find pure Python
modules in the filesystem supports that
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
I created issue4512 to implement get_filename extension in zipimport.
Will post a patch shortly.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +ncoghlan
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4512>
___
__
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
keywords: +patch
Added file: http://bugs.python.org/file12214/zipimport.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
I have attached a rough patch implementing the get_filename. I
deliberately copied code from get_source method that finds the filename
inside the zip archive and simply prefixed that with the archive path.
I could not fi
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4082>
___
_
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
See issue4512
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4082>
___
__
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
While the patch at issue4512 fixes the crash, it does not fix the line
number issue. I would prefer to start with doctest-1.patch like solution
because changing the PEP 302 loader protocol by adding get_filename needs
addi
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
In order to reproduce the reported problem I had to conjure the attached
repro.py which is missing '\n' on the last line.
I need to double check the language definition, but I feel this is not a
bug because a file t
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
According to my understanding of
http://docs.python.org/reference/lexical_analysis.html#id1
a newline character is required at the end of the python file.
___
Python tracker <[EMAIL
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Rafe,
Can you confirm that behavior on missing end-of-line is indeed your
issue? Note that at first I could not even reproduce the problem based
on your report.
I am attaching a proof-of-concept patch that would arguably i
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
Just to add to the list of getsource quirks: with the following in x.py,
f = lambda: 0 \
[EOF]
>>> import inspect, x; inspect.getsource(x.f)
Traceback (most recent call last):
..
tokenize.TokenError: ('EOF in multi
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Tue, Dec 9, 2008 at 11:02 AM, Mark Dickinson <[EMAIL PROTECTED]> wrote:
...
> If your Intel machine is Pentium 4 or newer, you can get
> around this by using the SSE2 extensions, which work with 64-bit doubles
>
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
You convinced me. After all, if python interpreter does not complain
about missing end-of-line and processes the unterminated line, getsource
should report it.
Here is a patch that passes existing tests and adds a "NoEOF
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
..
> The idea's attractive. The problem is finding an integer type that's
> guaranteed to have enough bits to store the mantissa for the float
> (probably plus one or two bits more for comfort); for IEEE
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
On Tue, Dec 9, 2008 at 12:39 PM, Mark Dickinson <[EMAIL PROTECTED]> wrote:
..
> What would using Python's integer type solve, that isn't already solved by
> the patch?
>
Speaking for myself, it would a
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4580>
___
_
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:
> I wonder if a patch for ctypes like this (which is not yet complete)
> could be used to implement this, or MUST it be implemented in C?
For the intended purpose of giving access to raw machine arithmetics, I
wou
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
Added file: http://bugs.python.org/file12323/ctypes-numbermixins-1.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:
--
nosy: +belopolsky
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3999>
___
_
Alexander Belopolsky added the comment:
Nick,
Your commit does not fix the line number reporting from doctest failures:
$ ./python.exe testmodule.zip
**
File "testmodule.zip/__main__.py", line ?, in __main__.c
...
Changes by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue4657>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
I've combined Scott's patch with John's (?) test case in issue1706039.diff.
Confirmed that the patch fixes the issue on Mac OS X
10.5.6 (Intel).
Added file: http://bugs.python.org/file12434/is
Alexander Belopolsky added the comment:
Maybe not a problem, but an inconsistency: in Py_UniversalNewlineFgets
clearerr is added inside univ_newline conditional and then again before
the loop over characters, but in Py_UniversalNewlineFread it is added only
once before "i
New submission from Alexander Belopolsky :
I am posting this patch mainly to support python-dev discussion on this
topic. In the past (see r45330) it was possible to compile python core
and standard library modules using a C++ compiler.
According to Martin v. Löwis (issue4665), "It&#x
Alexander Belopolsky added the comment:
A related question discussed on python-dev is whether extern "C" {}
wrappers should ever be used in .c files. I argue that the answer is "no"
even if C++ compilability is desired.
The new patch eliminates several uses of exter
Alexander Belopolsky added the comment:
On Fri, Jan 2, 2009 at 10:54 AM, Marc-Andre Lemburg
wrote:
>
> Marc-Andre Lemburg added the comment:
>
> Also note that by removing the extern "C" declarations, you not only
> change the exported symbol names of functions, but
Changes by Alexander Belopolsky :
Added file: http://bugs.python.org/file12560/c++-patch-2.diff
___
Python tracker
<http://bugs.python.org/issue4805>
___
___
Python-bug
Changes by Alexander Belopolsky :
Removed file: http://bugs.python.org/file12530/c++-patch-1.diff
___
Python tracker
<http://bugs.python.org/issue4805>
___
___
Python-bug
Alexander Belopolsky added the comment:
I believe attached issue4846.diff should fix the problem, but I don't
have access to the affected platform (Windows?), so I did not test it.
I also wonder whether it would be more appropriate to redefine PyAPI_*
macros to declare API symbols
Alexander Belopolsky added the comment:
On Mon, Jan 5, 2009 at 11:43 AM, Marc-Andre Lemburg
wrote:
..
>> GCC doesn't appear to do so, but there's no guarantee that other
>> C++ compilers won't touch these symbols:
>>
>> http://en.wikipedia.org/wiki/
Changes by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue4846>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
Not that it would matter on a two-line patch, but I find it useful to
add myself to the "nosy" list without any comments as so as I find the
issue interesting even if I have nothing to contribute at the moment.
This way I am more likely to n
New submission from Alexander Belopolsky :
quick_int_allocs, quick_neg_int_allocs, tuple_zero_allocs, and
fast_tuple_allocs are exported in -DCOUNT_ALLOCS builds. They should get
a conventional _Py_ prefix. Also since tp_allocs is now Py_ssize_t, these
should be redefined as Py_ssize_t as
Alexander Belopolsky added the comment:
On Mon, Jan 5, 2009 at 2:58 PM, Marc-Andre Lemburg
wrote:
..
> For completeness, all exported symbols in Python should have a _Py_
> prefix, even if they only get exported in certain debug builds.
>
I actually agree, but I felt that doing this
Alexander Belopolsky added the comment:
Attached patch is fairly straightforward with only one caveat: instead
of prefixing unlist_types_without_objects flag with _Py_, I made it
static. This may not be the right thing if it is intended to be
accessible from third party modules (it is not
Alexander Belopolsky added the comment:
Some more for both 2. and 3.0:
- 'as' is now a keyword
- 'with' is now a keyword
- @ is now a valid token
- 0o for octal and 0b for binary numbers
- sets
- str.format
- BaseException
I am sure I missed a lot, but the core languag
Alexander Belopolsky added the comment:
Martin,
Can you comment on whether unlist_types_without_objects should be global?
Svn blame point to you for introducing it.
Thanks.
$ svn blame Objects/object.c | grep unlist_types_without_objects
45527 martin.v.loewis int
Alexander Belopolsky added the comment:
This really belongs to python-list rather than the tracker. It is not
correct that with shell=False Popen reuses the thread of control of the
calling process. You seem to be confusing blocking and reusing the
thread of control. Popen always creates
Alexander Belopolsky added the comment:
On Tue, Jan 6, 2009 at 7:28 AM, Martin v. Löwis wrote:
..
> It is not easier, but more difficult. It now requires a change,
> whereas leaving things as-is requires no change.
I actually agree with Martin on this one. I would not touch this if
n
Alexander Belopolsky added the comment:
On Tue, Jan 6, 2009 at 10:53 AM, Marc-Andre Lemburg
wrote:
..
> I don't follow you: those symbols are not meant for public use anyway,
> so we can easily change them without any "costs". The same goes for any
> of the private, bu
Alexander Belopolsky added the comment:
The proposed patch appears to give up sorting by key,value altogether if
there are a few incomparable items. It would be better to group items by
type and sort within each group. For example,
pprint({1:1,2:2,A():3,A():4}) should print int:int items
Alexander Belopolsky added the comment:
On Wed, Jan 7, 2009 at 4:33 AM, Martin v. Löwis wrote:
>
> Martin v. Löwis added the comment:
> .. Furthermore, they all have names that are
> unlikely to collide. Even if they get a _Py_ prefix, there could
> still be a conflict.
>
M
Changes by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue4753>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Alexander Belopolsky :
With attached x.py:
$ cat x.py
"""
>>> foo()
"""
def foo():
1/0
if __name__ == '__main__':
import doctest, pdb
try:
doctest.testmod(raise_on_error=True)
except doctest.Unexpecte
Changes by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue4899>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
The OP's problem, i.e. the need to reimport modules in every docstring
can easily be addressed by injecting the necessary names using
extraglobs argument to doctest.testmod().
I like the following trick:
def getextraglobs():
import Str
Alexander Belopolsky added the comment:
> we decided some time ago to not accept patches for such minority
> platforms anymore.
I don't have any particular interest in BeOS variants, but this comes as
a surprise given that http://python.org/about/ proclaims that "Python
Alexander Belopolsky added the comment:
What is the rationale for swallowing all socket exceptions except
"Connection reset by peer" in __exit__? In any case, it is better to use
errno.ECONNRESET instead of literal 54.
Note that SMTP.quit() calls SMTP.close(), so in the normal t
Alexander Belopolsky added the comment:
On Mon, Jan 19, 2009 at 2:01 PM, Tarek Ziadé wrote:
>
> Tarek Ziadé added the comment:
>
>> What is the rationale for swallowing all socket exceptions except
>> "Connection reset by peer" in __exit__?
>
> I am catch
Alexander Belopolsky added the comment:
Please remove the old smtplib.patch: it is confusing to have two
attachments with the same name. It will still be available in the
history, so nothing will be lost.
A nit-pick: 221 is a success code (in smtp 2xx codes are successes and
5xx are errors
Alexander Belopolsky added the comment:
@pganssle - let's keep the substantive discussions in the tracker so that they
are not lost on github. You wrote:
"""
what is still blocking / needs to be done on this? Beta freeze for Python 3.10
is coming up at the beginning o
Alexander Belopolsky added the comment:
Is there high enough demand for nanoseconds in datetime and time instances?
How often nanosecond timestamps contain anything other than 0s or garbage in
the last three digits?
In my experience, all people want to do with such timestamps is to convert
Alexander Belopolsky added the comment:
> In telemetry,
a nanosecond often translates to about a foot and 5 hours gets you to Pluto.
Telemetry is exactly an application where absolute timestamps rarely make any
sense.
--
___
Python trac
Alexander Belopolsky added the comment:
> The work is now tracked at bpo-1635741.
Which work? bpo-1635741 does not appear to be a meta-issue and in msg381432 it
loops back here.
--
versions: +Python 3.11 -Python 3.4
___
Python tracker
<
Alexander Belopolsky added the comment:
I'll reopen this issue to resume the discussion. The motivating case - PEP
3121 refactoring of the ctypes module - is still open. See bpo-15884.
--
resolution: rejected ->
stage: resolved -> patch review
status: closed ->
Alexander Belopolsky added the comment:
Can someone try to replicate this while disabling the C acceleration:
import sys
sys.modules[‘_datetime’] = None
(Before any other imports.)
If anything, this is likely to be a problem with the C implementation
Change by Alexander Belopolsky :
--
dependencies: +Add timezone support to datetime C API
___
Python tracker
<https://bugs.python.org/issue30155>
___
___
Pytho
New submission from Alexander Belopolsky :
Let g be a an invalid time in New York spring-forward gap:
>>> g = datetime(2020, 3, 8, 2, 30)
According to PEP 495, conversion of such instance to UTC should return a value
that corresponds to a valid local time greater than g, but
Alexander Belopolsky added the comment:
> On Mar 2, 2020, at 6:33 PM, Gregory P. Smith wrote:
>
> Change that default to any old year with a leap year (1904?)
In the 21st century, the year 2000 default makes much more sense than 1900.
Luckily 2000 is also a
Alexander Belopolsky added the comment:
I am sure this has been reported before – I will try to find the relevant
issue. This behavior is correct and documented. The only improvement that we
can consider is to make it more explicit that utcnow is deprecated and the
correct way to obtain
Alexander Belopolsky added the comment:
This is a duplicate of issue 33293.
--
superseder: -> Using datetime.datetime.utcnow().timestamp() in Python3.6.0
can't get correct UTC timestamp.
___
Python tracker
<https://bugs.python.org
Change by Alexander Belopolsky :
--
resolution: wont fix -> duplicate
___
Python tracker
<https://bugs.python.org/issue39970>
___
___
Python-bugs-list mai
Alexander Belopolsky added the comment:
I agree that having some of datetime.now([tz]) functionality replicated in
datetime.today() makes little sense. However, the presence of this method in
datetime class is a consequence of datetime being a subclass of the date class.
The latter was a
Change by Alexander Belopolsky :
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
1501 - 1600 of 3596 matches
Mail list logo
