apache / apache/pulsar-client-python
[Investigation] Fully-native Python client
- Linguagem predominante
- Python
- Estrelas
- 75
- Forks
- 53
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
I'm rather new to this project but, I thought it might be worthwhile to gauge the community's thoughts on implementing a fully-native Python client. Those of you who have a more intimate understanding of the internals, my questions would be:
- Is it feasible that a native Python client be developed, or are there any potential show-stopping limitations (i.e., the C++ client can handle some task that Python isn't well-suited for)
- Given that it is feasible, is the investment of effort worthwhile? Or is wrapping functionality from the C++ client a better approach at least in the short-medium term?
- Any other thoughts along these lines?
Also, if there is a better venue for starting this conversation (i.e., the main pulsar repo, the C++ client repo, or the dev mailing list) let me know and i'll close this and start it there. I just had the thought that maybe those who have worked with the Python client specifically might have a clearer understanding of the pros and cons of going in that direction.
Guia de contribuição
Direção de pesquisa
Comece revisando o cliente Python e o cliente C++ para entender seus respectivos componentes internos e capacidades. Compare se Python pode oferecer a funcionalidade necessária sem fazer wrapping de C++, e então documente a viabilidade, as limitações e a direção recomendada para a comunidade.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- cpp, python
- Domínio
- api, distributed-systems
- Tipo de issue
- Funcionalidade
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100