Duplicate project with same purpose and motives

[AlmogCohen]

I've just released https://pypi.org/project/protobuf-schematics/ and I'm pretty frustrated LOL! I've implemented it with the exact same requirements in mind and same motives...found your project only when I was searching for my own release on PyPi. Unbelievable... The only difference is that I based my project over pyrobuf which is pure python based parser which does not require protobuf installed. I liked the way your README is explaining the motive 👍

I was looking for such a library for quite sometime with no success so I made it now...I post it here because:

1. I still can't believe it.
2. I'll give other people in the future the opportunity to choose...(altough I'll might end up using your project).

Anyway, I'll spend some time tomorrow to look into the work that has been done here.

P.S. You can probably close this issue once its acknowledged :)

[AlmogCohen]

Actually I think that the only difference is that my project does not require the protobuf compilation component and is based on the pyrobuf pure python parser. Also, mine is still incomplete with supported types as I implemented only what I've needed.

Also, I've implemented Schematics EnumType that might be useful also for some people using this repo. Maybe you did it as well and I've missed that.

[gabisurita]

@AlmogCohen Hey, this project is not currently maintained, so I believe we can try to deprecate it in favor of your implementation.

Supporting the native Google implementation is a nice to have IMO. Maybe we can try to add support for both pyrobuf and Google Protobuf implementations?

[AlmogCohen]

I like the official ProtoBuf suppot too. PyroBuf had not implemented full support for everything in the protocol. On my side I like the generation of actual python file with all the classes defined. I can enjoy then the IDE's auto-completion for quick development. I also think that the EnumType is useful and the conversion of map fields to DictType. Anyway, I don't mind merging most of the good stuff into your repo or vice versa. I don't believe I'll invest much work in the future as I needed that for a project I'm working on now and have got all support I needed. Probably your did the same :) What do you think? I do think it would be nice to deprecate one in favour of the other though to support future development efforts if someone will find it useful. Thanks! :)

…

On Mon, Jan 14, 2019, 05:56 Gabriela Surita ***@***.*** wrote: @AlmogCohen <https://github.com/AlmogCohen> Hey, this project is not currently maintained, so I believe we can try to deprecate it in favor of your implementation. Supporting the native Google implementation is a nice to have IMO. Maybe we can try to add support for both pyrobuf and Google Protobuf implementations? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADtXZu6ynaRZSNGw4TueX6Zdsyd-02B8ks5vDIyUgaJpZM4Z9s43> .