fix pyroclient

[MateoLostanlen]

Following PR #204, the pyroclient commit was not fixed in src

I don't realy get the point of having two pyproject.toml @RonanMorgan @frgfm any thoughts ?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.30%. Comparing base (0a1ae7c) to head (409fd1c).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #213   +/-   ##
========================================
  Coverage    92.30%   92.30%           
========================================
  Files            6        6           
  Lines          507      507           
========================================
  Hits           468      468           
  Misses          39       39           

Flag	Coverage Δ
unittests	92.30% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[frgfm]

Hey there, sorry I don't get what you mean? I can only see one pyproject.toml

If you mean setup.py and pyproject.toml it's because the setuptools team and the core Python teams haven't yet agreed to a unified way of doing things. It will go away (hopefully soon)

[MateoLostanlen]

Hi @frgfm no here we have pyproject.toml and src/pyproject.toml. Can't we unite them in one file?

[frgfm]

My apologies! To be honest, I haven't contributed much to this repo in a while 😅
Back then, I think we had those separated so that the library can be used as standalone lib, but now I don't see any reason to have different pyproject and yup I agree this should be unified and similar to the API (in the sense that we need accurate version pinning, not upper/lower bound so poetry)

Happy to help if we need to make the docker image lighter & clean the build process 👌

[MateoLostanlen]

Ok thanks for your answer. completely agree. I'll merge this pr to fix the bug then I'll make another to unify based on the pyro-api model