Workaround pintpandas iter issue

[andrewgsavage]

• Closes # (insert issue number)
• Executed black -t py36 . && isort -rc . && flake8 with no errors
• The change is fully covered by automated unit tests
• Documented in docs/ as appropriate
• Added an entry to the CHANGES file

Possible work around for the iter issue
Drops the failing tests from
====== 21 failed, 329 passed, 29 xfailed, 2 xpassed, 6 warnings in 21.44s ======
to
====== 4 failed, 346 passed, 28 xfailed, 3 xpassed, 11 warnings in 17.55s ======

hgrecco/pint-pandas#33
see also
#753

[znicholls]

Super nice @andrewgsavage !

[hgrecco]

awesome

[hgrecco]

There are a few failing tests.

[znicholls]

There are a few failing tests

One thing I noticed, we'll need a hack to workaround e.g. Quantity("1", "m") because strings are iterable :(

[andrewgsavage]

(Tiny typo) magnitide —> magnitude
haha ty, didn't notice that when debugging and was confused

OK sounds like you're happy with this approach, will try to get this working.

[hgrecco]

I have to say that I was surprised that it worked. A few years ago I tried doing this with the __str__ method but it did not work. But I think that __iter__ is different.

Can you also try in this PR to change the imports from pintpandas to pint_pandas (I posted the change here hgrecco/pint-pandas#1)

Not required any more, done in #1127

[hgrecco]

I was trying to fix the pending issues without success. Likely because Magic methods like iter are looked up on the class, not the instance as described here. I will release pint-pandas and then maybe we should rediscuss if we create a Quantity class that inherits from numpy array.