project status?

Hi, I've noticed that other than a PR being applied a year ago, there haven't been any commits in 3 years.

Also, setup.py's classifiers merely lists Python3 rather than specific versions and it's listed as 'Beta' software.

Is this software still being maintained (either in this repo or by some other fork)? I think I have a good use case for this package, but I don't want to use it if it's been abandoned.

Hi. Thank you for your interest. This software is not maintained anymore. Use at your own risk.

Thank you for your interest.

I had too little feedback from the users, zero contributions, and I thus lost interest. How could I ever find a successor ?? Also, I developed too many functionality, and changed the core algorithm to gain performance, but I suspect I introduced bugs by so doing.

Best regards Pierre c.

On Sunday, October 7, 2018, Max Heiber [email protected] wrote:

Is there a post on what was learned from the project and what worked well, didn't work well, what the successors are? It seems like incredible stuff, I was surprised to see that it's not maintained!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pcarbonn/pyDatalog/issues/28#issuecomment-427623586, or mute the thread https://github.com/notifications/unsubscribe-auth/AAa5aR-d8owGL3TzUSSYj4Ze2q0Fm5TFks5uiXmegaJpZM4Wkusj .

For what it's worth, Pierre, I have used pydatalog in this project: https://github.com/AlgorexHealth/hcc-python

I came here because I was looking to understand your implementation of tabling.

Even though it's not still maintained, I thank you for your work on it.

Thank you. It's good to know. Let me know if I can help. PC

Le mar. 16 oct. 2018 16:22, reverendpaco [email protected] a écrit :

For what it's worth, Pierre, I have used pydatalog in this project: https://github.com/AlgorexHealth/hcc-python

I came here because I was looking to understand your implementation of tabling.

Even though it's not still maintained, I thank you for your work on it.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pcarbonn/pyDatalog/issues/28#issuecomment-430257217, or mute the thread https://github.com/notifications/unsubscribe-auth/AAa5aZETYCMbcmfY0bNZOcq_T5YVboFmks5uleu9gaJpZM4Wkusj .

Hi pcarbonn，

I am using pyDatalog to build the SDN tool(TupleNet) which can construct virtual-networking. And TupleNet was used in vipshop. So I am here to let you know the pydatalog is a awesome tool.

And also want to know if you would like to make incremental-update happen in pyDatalog?

https://github.com/vipshop/TupleNet

I am finding pydatalog a bit hard to learn, as I am new to logic programming, and it is not clear to me how to approach many things.

I was hoping to find more examples, and disappointed the project is no longer active.

Thank you for your interest. I had too little feedback from the users, zero contributions, and I thus lost interest. How could I ever find a successor ?? Also, I developed too many functionality, and changed the core algorithm to gain performance, but I suspect I introduced bugs by so doing. Best regards Pierre c. … On Sunday, October 7, 2018, Max Heiber @.***> wrote: Is there a post on what was learned from the project and what worked well, didn't work well, what the successors are? It seems like incredible stuff, I was surprised to see that it's not maintained! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAa5aR-d8owGL3TzUSSYj4Ze2q0Fm5TFks5uiXmegaJpZM4Wkusj .

A pity pydatalog didn't see mainstream adoption. It is such a cool library. You mentioned that you changed the core algorithm and that may have introduced bugs. Is it possible to list the library version before the core algorithm was changed? I can then just pip install that version and learn more about the ideas behind pydatalog.

Thanks. Looking at the change log I suspect that version 0.15.2 would be better. Version 0.16 had a major rewrite of the resolution engine, and I suspect it was not so good.

Thanks!