Is this repository still maintained?

[jd]

I see many issues and pull requests without any response.

Is this still being maintained and worth contributing? Anything the community can do to help?

[ilevkivskyi]

Unfortunately, we didn't have much time for this lately. @JukkaL what do you think we can do?

[heckad]

Could you submit the project to the sqlalchemy community?

[Fruglemonkey]

Would love if #149 could make it into a release - this solves many long-standing annoyances we have at my org!

Maybe it is an idea to get new maintainers on board who do have time?

[ilevkivskyi]

There is a plan to switch to modular typeshed, see python/typeshed#2491. One possible option is when this will be implemented, we can probably transfer stubs there, so they will be community maintained. It is not clear however what to do with the plugin, making changes that requires coordination between mypy plugin and stubs will be harder.

[ilevkivskyi]

Btw, I am going to make a release later today. Please test the current master to check if there are any issues.

good to see some activity again!

[ilevkivskyi]

I finally released sqlalchemy-stubs v0.4 on PyPI. Please try it!

[wbolster]

thanks @ilevkivskyi it's really appreciated 🙏

[Spindel]

I'm still missing the omit_join and sync_backref arguments from #169, I've rebased against master and will run our lints against that.

[Spindel]

With #169 applied, our stuff goes through neatly with 0.4 release. Cheers!

[zzzeek]

@ilevkivskyi we are at the point now where I have time to start looking at this, as SQLAlchemy 1.4.0b2 is released, 1.4 will be next, and from there we go into 2.0 which is Python 3 only. I'd like 1.4 to have mypy support and the internals have changed enough that SQLAlchemy should first be publishing its own .pyi files + plugin, then in 2.0 it would likely all be included inline including the plugin. I observed today that mypy needs a plugin even for Python's own dataclasses, so it looks like plugins are a fixed requirement to support this kind of thing.

[ilevkivskyi]

Great news!
Yes, a plugin is required for mypy, but it should be easy to ship it with the distribution, it is just a moderate size module. Also it is easy to enable in mypy configs, moreover I think people who have it already configured will not need to update configs after moving the plugin to SQLAlchemy (assuming you keep the module name).