Pendulum VS Pylint

I did the same with datetime and moved to using Pendulum.

Python could be better but really, does any language handle date and time types well? After 30+ years of this I mostly just use seconds since epoch everywhere like some sort of caveman banging rocks together. But at least it works clearly.

Last I looked Pendulum was the best choice for a fancy but humane Python library for dates and times. Install size is over 4MB :-( https://pendulum.eustace.io/

Good luck with your library, but for everyone else I’ll leave this here: https://pendulum.eustace.io/

Pendulum is quite good[0]. Relatively intuitive interface.

When I left Rails, this is one area I really missed.

Time.use_zone("Singapore") { (Time.zone.now - 3.days).beginning_of_week }

This readable line in datetime utils or even pendulum, is such a pain.

[0] https://github.com/sdispater/pendulum

You shouldn't do manual date and time calculations, there are people dedicated to developing tools for that and they're giving those tools for free! An example, Pendulum for Python.

Yes, the datetime api once timezone is involved is quite bad in python.

This is why for anything that uses timezone, I use pendulum: https://pendulum.eustace.io/

It's compatible with the datetime api, but it has sane default, nice tools to convert between timezone, some cool date adjustment stuff, and can humanize time in several languages.

Basically, datetime has the same problem as text vs raw bytes in python 2.7, except it has never been fixed.

Bless you for using the stock library but Pendulum is a much more humane way to work with dates and times in Python.

Also, check the docs here if you're open to an alternative: https://pendulum.eustace.io/

Use Pendulum. It makes converting, adding and subtracting times trivially simple.

A little introduction about pylint. Pylint is a static code analyzer, it analyses your code without actually running it. Pylint looks for potential errors, gives suggestions on coding standards that your code is not adhering to, potential places where refactoring might help, and also warnings about smelly code.

Pylint, on the other hand, focuses on code analysis and style checking. It offers extensive customization options and supports various coding standards. Pylint is known for its comprehensive reports and ability to detect a wide range of code issues.

In my opinion, the best way to expose configuration options is to read and parse them from the project's pyproject.toml file. Here's how Pylint handles it.

I even contributed to Pylint by submitting a new rule a few years ago : implicit-str-concat.

Implemented code formatting with Black and linting with Pylint in my CI pipeline. Here is my updated GitHub Actions Workflow file: ci.yml

One last thing to do before running the hooks is to create a config file, just like we did with flake8. For this you are going to create a pylintrc file at the roor of your project and copy the contents of the pylintrc file from the pylint repo (here is the link to it).