Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is this Project Dead? #958

Closed
benjamin-small opened this issue Jan 10, 2023 · 6 comments
Closed

Is this Project Dead? #958

benjamin-small opened this issue Jan 10, 2023 · 6 comments

Comments

@benjamin-small
Copy link

I'm looking through I'm not seeing responses from the developers or code commits. Is anybody still working on this?
@DEAN-Cherry
Copy link

Try this
https://neo4j.com/docs/getting-started/current/languages-guides/neo4j-python/

@phreakocious
Copy link

phreakocious commented Mar 29, 2023 •
edited
Loading

Bumping the question before I get too attached to OGM and have to dump it. It would be nice to not be doing tons of low level stuff to load nodes and edges.

@jkminder
Copy link

Sadly yes, the main dev Nigel Small answered this on twitter:

Thanks Julian. No, I've not been at Neo4j for over a year and a half now, and I'm no longer involved with the community. When I left, I tried to find someone else to take it on but was unsuccessful. I would suggest you consider it EOL, and look to the official driver instead.

— Nigel Small (@technige) April 19, 2023

Maybe the community can take it over.

@technige
Copy link
Collaborator

Yes, please now consider py2neo to be EOL. I do not plan to make any more updates and am currently considering whether or not to renew the domain names next month.

During my decade-long involvement with Neo4j, there was never any interest from the company in providing official staffing for the project. On leaving back in 2021, I was also unable to find a maintainer.

Given that so much time has now passed, the code will be very out of date. At least one major release, plus a bunch of other features have been shipped since I last worked on this. Therefore, another maintainer would likely have a very difficult job catching up.

I would strongly suggest looking to the official drivers as a replacement. Although I know that the functionality provided there is slimmer, the team of engineers I left behind are fantastic.

Thank you to everyone for making this such a fun part of my life. It's now time to move on.

Nigel ❤️

@technige technige pinned this issue May 19, 2023
@cdboer cdboer mentioned this issue May 19, 2023
Open
@technige technige mentioned this issue May 19, 2023
Closed
elena referenced this issue in elena/py2neo May 20, 2023
@elena
#958 Update README.rst with official links
a6d6379 
Thank you so much Nigel 💖.

Maybe one day there could be another maintainer? But if so forking is always possible. 

Good Luck and Thank you for your hard work.
@phreakocious
Copy link

Anyone looking for an alternative should take a look at neomodel .. It offers a similar OGM solution and syntax and is back under active development.

@jclock98 jclock98 mentioned this issue Oct 23, 2023
Closed
@Thiago-Reis-Porto
Copy link

It's available again in https://pypi.org/project/py2neo/, and for older specific version on https://pypi.org/project/py2neo-history/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@technige @phreakocious @benjamin-small @jkminder @Thiago-Reis-Porto @DEAN-Cherry