reproducibility, patterns, pythonisms

[JacobFV]

Thank thank you thank you Anton. You won. My dream of building ComputaCode is probabbly over. lol. It's okay. I'm happy for everyone else.

For reproducibility purposes, I recommend using poetry since it records package versions. Also it simplifies building wheels and publishing.

I've updated the configured for poetry, reorganized some files to follow the pythonic conventions, and updated referenced. Please see my fork.

[JacobFV]

Had to make some more changes to get poetry to work from the CLI. But now you should have entry points that pipx recognizes.

[JacobFV]

Ready to merge

[AntonOsika]

Thanks so much for the PR!

There are some conflicts now, and I can't fix them before merge.

If you do it I'd be happy to merge.

Also: do you want to delete pycache files and my-new-project directory? ❤️

[JacobFV]

Thanks so much for the PR!

There are some conflicts now, and I can't fix them before merge.

If you do it I'd be happy to merge.

Also: do you want to delete pycache files and my-new-project directory? ❤️

Thanks. I see.

Away from home rn but will commit in about an hour

Yes

[JacobFV]

I think this is ready to merge, but Github won't let me. I'm able to finish with my permissions tho:

[AntonOsika]

Thanks @JacobFV!

To resolve the conflicts you need to do a pull on the main branch of the repo.

I.e. something like:

git remote add upstream https://github.com/AntonOsika/gpt-engineer

git pull upstream

And then resolve conflicts (I use pycharm to resolve but up to you ofc)

[patillacode]

Closing, more context in #38

Thanks @JacobFV

[JacobFV]

Hi, been busy. Thank you