DEV Community: mbarkhau

Pretty Traceback - Human Readable Stacktraces for Python

mbarkhau — Mon, 17 Aug 2020 07:55:00 +0000

Pretty Traceback groups together what belongs together, adds coloring and alignment. All of this makes it easier for you to see patterns and filter out the signal from the noise.

https://pypi.org/project/pretty-traceback/

Pylint-Ignore - Get Started Using Pylint

mbarkhau — Sun, 26 Jul 2020 17:47:06 +0000

I have a few projects that I haven't been using Pylint for and after recently running into a bug that I know would have been caught by it, I decided that needed to change and so I created this project Pylint-Ignore

This allows me to start using Pylint and catch any bugs in new code I write and gradually burn down the backlog of possible issues in my projects. I think this is a better approach than having to configure everything at the start and having to clean up my whole project before I can add Pylint to my CI setup.

I hope you find this useful and look forward to your feedback.

Python lib3to6: The Bablejs of Python now has support for Python 3.8.

mbarkhau — Sat, 22 Feb 2020 20:44:42 +0000

I just published an update to lib3to6.

This release adds support for

the new bpo36774 f-string = specifier
and of course the infamous := walrus operator (except inside comprehensions).

While these are nice, the main use case of lib3to6 remains that you can use the type annotation features during development (some of which are only available on 3.6+) without having to sacrifice compatibility when you publish your packages. Support Python 3.5 with minimal extra effort, or even 2.7 if you still care about that.

lib3to6 - python compatability library

mbarkhau — Tue, 14 Jan 2020 00:50:39 +0000

In light of the recent blog article "Mercurial's Journey to and Reflections on Python 3" by Gregory Szorc I thought I'd try to pimp my work in this area again.

In short, if you have a project that needs to be compatible with Python 2.7 or even just Python 3.4, then you might want to look at lib3to6. The idea is quite similar to Bable for JavaScript: It transforms valid Python 3.7 code, into valid Python 2.7 code such that the semantics match as closely as possible.

I still work with a Python 2.7 codebase, but most new work is now done in modules that are written for Python 3.7 and this library translates the code when the package is created. I've used it over the past year on half a dozen projects and I feel it is quite stable.

An example of how it works.

Say you have a my_module which is written for Python 3.7. Features used here that are not supported by Python 2.7 are

type annotations
f-strings
print function
implicit utf-8 file encoding

# my_module/__init__.py
import sys


def hello(who: str) -> None:
    print(f"Hello {who} from {sys.version.split()[0]}!")


print(__file__)
hello("世界")

The above code is translated to the following

# -*- coding: utf-8 -*-
from __future__ import absolute_import
from __future__ import division
from __future__ import print_function
from __future__ import unicode_literals

import sys


def hello(who):
    print('Hello {0} from {1}!'.format(who, sys.version.split()[0]))


print(__file__)
hello('世界')

Some changes that are made:

Explicit utf-8 file encoding
Future import boilerplate. This changes the semantics to match those of Python 3, i.e.:
- print is a function
- string literals are unicode literals
f-string converted to an equivalent string.format invocation.

I've had some people puh puh the project, because the gut reaction appears to be that Python 2.7 should die already, but this project is also useful if you are a library author who, for example, wants to use f-strings and yet still have your library be compatible with Python 3.5. If you don't care about Python 2.7 then just don't test for it.

There is much more that could be said, but I think this is enough for now and I hope you find the library useful.

AsciiGrid - A WYSIWYG Editor for ASCII Diagrams

mbarkhau — Mon, 30 Dec 2019 21:06:32 +0000

I like to use Ascii diagrams in my documentation, but they are a pain to edit in a traditional text editor. To solve this I wrote AsciiGrid over my Christmas break.

The mobile experience is probably not great and I haven't tested on Mac or Windows. If you have any issues, please report them or send patches to gitlab.com/mbarkhau/asciigrid

Here are some more examples from the svgbob page

I hope you find it useful, cheers.