remove requirement for requirements.txt when specifying dependencies for deploying to functions: support poetry

Functions Framework is fantastic! BUT, it looks like there is a requirement to have requirements.txt for dependencies in cloud functions? Is that a functions framework issue? Or a GCP Functions limitation? Ex: would there be somewhere else to take this concern?

Since we generally now use poetry to define our dependencies, that means functions-framework needs a 'special' requirements.txt for dependencies if deploying to GCP Cloud Functions? Is there any known workaround?

Thanks!