Gabriele Pongelli

a cool improvement could be using "dedicated parser" for each supported file format (toml, yaml, json...) , reverting to actual regex way in case dedicated parser does not exist, but...

I've just made [a PR to your repo](https://github.com/SensorsIot/IOTstack/pull/23) .

[this PR](https://github.com/commitizen-tools/commitizen/pull/550) should fix, can you try it and see if the `UnicodeDecodeError` still happens ?

@Woile is it reasonable to add a test with single emoji character as changelog?

> > @Woile is it reasonable to add a test with single emoji character as changelog? > > You mean someone create a commit with only emoji character and later...

> Using `truststore` with `httpx`... > > ```python > import httpx > import ssl > import truststore > > ssl_context = truststore.SSLContext(ssl.PROTOCOL_TLS_CLIENT) > client = httpx.Client(verify=ssl_context) > ``` you saved...

this happens also with poetry 1.4 . other OS does not suffer this issue.

as per [my comment on poetry-core](https://github.com/python-poetry/poetry-core/pull/555#issuecomment-1463793525), that PR fixes this issue. Thanks,

I've had same issue building a C extension with Poetry, following online examples like [FirefoxMetzger/mini-extension](https://github.com/FirefoxMetzger/mini-extension) and [Lucky-Mano/Poetry_C_Extension_Example](https://github.com/Lucky-Mano/Poetry_C_Extension_Example), they both use the convention to call build script "build.py" Changing file name...

I confirm those changes works like a charm 😃