Remove pypy and python2 from tox and travis.

[kishan3]

This should help one step in closing #727

[codecov]

Codecov Report

Merging #744 into master will decrease coverage by 0.37%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #744      +/-   ##
==========================================
- Coverage   95.61%   95.23%   -0.38%     
==========================================
  Files         304      304              
  Lines        2646     2646              
==========================================
- Hits         2530     2520      -10     
- Misses        116      126      +10     

Impacted Files	Coverage Δ
dateparser/utils/strptime.py	92.68% <0.00%> (-7.32%)	⬇️
dateparser/utils/__init__.py	94.81% <0.00%> (-2.23%)	⬇️
dateparser/search/search.py	98.06% <0.00%> (-1.30%)	⬇️
dateparser/date.py	99.15% <0.00%> (-0.43%)	⬇️
dateparser/languages/locale.py	98.39% <0.00%> (-0.27%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b546ad...a919398. Read the comment docs.

[Gallaecio]

The coverage data reveals a few parts of the code that are specific to Python 2 and can be removed.

[noviluni]

The coverage data reveals a few parts of the code that are specific to Python 2 and can be removed.

@Gallaecio , let's do this in a next PR!

[lopuhin]

re pypy removal - maybe it makes sense to add pypy3 then, maybe as part of another PR?

[noviluni]

Hi @lopuhin, I tried it and the tests were totally broken. The regex package doesn't have official support for pypy and pypy3. I would love to have support for pypy3, but I think it's not as easy as it seems (maybe it's not possible) and it should be added in another, different, PR. Thank you for your comment, I opened this new ticket to discuss it: #745

[noviluni]

Anyway, this is the first step on a list of steps to get rid of Python 2.

We will:

• Remove Python 2 testing (this will make it easier to create new PRs without needing to support Python 2.7)
• Update setup file
• Migrate code (probably using 2to3 and checking it carefully)
• Delete other reminiscences (the six package, version-specific code...)

We don't need to perform these steps in this strict order, but I think it's a good way to go, let me know if there is any wrong on this approach or if you have any other idea.

@Gallaecio @lopuhin

[lopuhin]

Thanks @noviluni yes makes sense to tackle pypy3 separately. Re the steps you outlined - they make sense, I don't have experience with 2to3, only with manual porting, but usually py2-specific code stands out.

[kishan3]

Hi @noviluni @Gallaecio we should merge this only after coverage is fixed or can do now?

[Gallaecio]

Hi @noviluni @Gallaecio we should merge this only after coverage is fixed or can do now?

I think we can merge already and tackle the coverage part separately, as @noviluni suggested.

[noviluni]

Good job! Now we can say that we don't support Python 3 officially 🤣