Hi.

I've been trying to use Moment with Python 3.4 and got this:

In [1]: import moment

In [2]: moment.now().subtract(monthes=6)

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-2-9407b0856ff3> in <module>()
----> 1 moment.now().subtract(monthes=6)

/usr/lib/python3.4/site-packages/moment/date.py in subtract(self, key, amount, **kwds)
     65         """Subtract time from the original moment."""
     66         if not key and not amount and len(kwds):
---> 67             for k, v in kwds.iteritems():
     68                 self.subtract(k, v)
     69         if key == 'years' or key == 'year':

AttributeError: 'dict' object has no attribute 'iteritems'

String provided by repr of date is misleading:

>>> import moment
>>> m = moment.date("11-12-2012", "M-D-YYYY")
>>> repr(m)
'<Moment(11-12-2012)>'
>>> m2 = moment.date("11-12-2012", "D-M-YYYY")
>>> repr(m2)
'<Moment(11-12-2012)>'
>>> m.date
datetime.datetime(2012, 11, 12, 0, 0)
>>> m2.date
datetime.datetime(2012, 12, 11, 0, 0)

As you see, while the dates are different, strings returned are equal:

>>> m == m2
False
>>> repr(m) == repr(m2)
True

This is against convention, that repr tries to represent the value as precisely as possible.

Proposal: print the value as ISO formatted string.

$ pip3 freeze | grep moment
moment==0.10

>>> import moment
>>> import datetime
>>> moment.date(datetime.date(2020, 1, 1)).subtract(months=1).isoformat()
'2020-12-01'

was expecting 2019-01-01

Is it a bug or undocumented feature? Not sure if I understand it. Thanks in advance.

In [1]: import moment

In [2]: moment.date('2000').date
Out[2]: datetime.datetime(2000, 7, 1, 0, 0)

Set out to fix the deprecated pip install --use-mirrors but ended up introducing tox to test against multiple versions of python and have travis use this.

When I use something like moment.utcnow().add(years=3, months=2).format("YYYY-M-D h:m A") i get a type error that says integer argument expected, got float. How should I go about resolving this issue? I have tried a couple of things, but couldn't seem to get it to work as expected.

Hello,

I need to parse dates easily with different formats and moment is amazing for this, and I thank you very much for your work!

As you may or may not know, the US always does stuff differently than the rest of the world and, for example, display their dates month first (which IMO makes no sense) but makes it a hassle for parsing.

See my example here:

>>> moment.date("11/05/2022").strftime("Month: %m, Day: %d, Year: %Y")
'Month: 11, Day: 05, Year: 2022'

Whereas I would've expected it to output the 11th of May... I tried using the .locale() method but it didn't fix it. Any idea ?

moment.unix(t).epoch() does not equal t.

t = 1653430533339. # GMT: Tuesday, May 24, 2022 10:15:33.339 PM moment.unix(t).epoch(). # 1653405333 -> GMT: Tuesday, May 24, 2022 3:15:33 PM

Hi, I am a high school student just starting to learn about testing techniques. I found a bug in the latest version (0.12.1) of moment while doing some fuzzing using the fuzzing tool Atheris. The reproducing process is shown below:

import moment
moment.date('2001W5')

Results <Moment(1984-01-03T17:32:28)>

My Environment

Python 3.8.10 (default, Mar 15 2022, 12:22:08) 
[GCC 9.4.0] on linux 
moment in /home/clou5/.local/lib/python3.8/site-packages (0.12.1)

I am still not very sure about the bug so I would very much appreciate any kind of feedback regarding it. Thanks.

@classmethod def diff(cls, start_time: Moment, end_time: Moment, diff_type=None): if not diff_type: diff_type = 'seconds' start = cls.get_current_moment(start_time) end = cls.get_current_moment(end_time) return end.diff(start)

This method fails:

moment.date(time_delta).add(weeks=week_range)

And returns this error:

  File "C:\Python39\lib\site-packages\moment\date.py", line 50, in add
    self.add(k, v)
  File "C:\Python39\lib\site-packages\moment\date.py", line 56, in add
    self._date += timedelta(weeks=amount)
TypeError: unsupported operand type(s) for +=: 'int' and 'datetime.timedelta'

(venv) wangchengjie@wangchengjies-iMac coverity % python --version   
Python 3.6.8

The below code produced conflict results when I compared it with datetime

    from moment import Moment, now
    a = now()
    print(a)
    a.timezone('America/Los_Angeles')
    print(a)
    from datetime import datetime
    from dateutil import tz, zoneinfo
    tz_pst = tz.gettz('America/Los_Angeles')
    print(datetime.now())
    d = datetime.now(tz=tz_pst)
    print(d)

output:

2022-03-15T03:30:45+08.00
2022-03-14T20:30:45+08.00
2022-03-15 03:30:45.220210
2022-03-14 12:30:45.220222-07:00

There is a recursive error (probably on line 60 of file moment/date.py you have to return in order to avoid the replication of the operation). I add to you two examples, the first shows the error with moment, the second abstracts the error in a python primitive way.

import moment

start = moment.date('2021-12-01T18:49:25.902586+0000').locale('utc')

print(start.add(days=30).datetime)

class Tester:

    def __init__(self):
        self.ab = 1

    def test(self, i=0):
        if i == 0:
            for x in ['test']:
                self.test(i=1)

        self.ab += 1

        return self


t = Tester()

print(t.test().ab)

I used "probably" above because the problem seems to appear and disappear without any logic.