# \[tor-dev\] Release new version of stem
**URL:** https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551
**Category:** tor-dev
**Created:** [September 16, 2022, 10:39am UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551 "2022-09-16T10:39:35Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Hefee](https://forum.torproject.org/u/Hefee)
#### Post date: [September 16, 2022, 10:39am UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/1 "2022-09-16T10:39:35Z")
Hey,
nodens(nodens@debian.org) and me are currently packaging the new version of
onionshare for Debian and stumbled over the dependency cepa[1], what is a fork
of stem. After digging deeper into it, I found out, that the main reason why
they do so is the support for Client Auth v3 onions[2]. I really would like
not to package a fork of stem, if possible. That's why I ask, when it is
planed to release a new version of stem? It hasn't seen any release since 2019
and there are a lot of changes in master branch too. Maybe you can just
release the current state of the maint branch, that is actually what is
released as cepa 1.8.3.
I some how need to solve this till January, when Debian is freezing (not
accepting new versions).
Regards
hefee
[1] [GitHub - onionshare/cepa: Python controller library for Tor](https://github.com/onionshare/cepa)
[2] [don't use deprecated int\_from\_byte to test cryptography · torproject/stem@4e3917c · GitHub](https://github.com/torproject/stem/commit/)
2f3bbf64b4ce3b63160a3c56b15748ba626de4a0
---
### Author:  [@GeKo](https://forum.torproject.org/u/GeKo)
#### Post date: [September 16, 2022, 3:18pm UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/2 "2022-09-16T15:18:07Z")
Hefee:
> Hey,
>
> nodens(nodens@debian.org) and me are currently packaging the new version of
> onionshare for Debian and stumbled over the dependency cepa[1], what is a fork
> of stem. After digging deeper into it, I found out, that the main reason why
> they do so is the support for Client Auth v3 onions[2]. I really would like
> not to package a fork of stem, if possible. That's why I ask, when it is
> planed to release a new version of stem? It hasn't seen any release since 2019
> and there are a lot of changes in master branch too. Maybe you can just
> release the current state of the maint branch, that is actually what is
> released as cepa 1.8.3.
>
> I some how need to solve this till January, when Debian is freezing (not
> accepting new versions).
That is tricky as stem is not maintained anymore and therefore deprecated. There are no further releases planned and talking to atagar last time he said the master branch was not ready for release. We could think about minor point releases for the 1.8 series but those would just contain small bug fixes (like Python 3.10 compatibility) but no new features.
Hope this helps,
Georg
---
### Author:  [@Hefee](https://forum.torproject.org/u/Hefee)
#### Post date: [September 17, 2022, 11:06am UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/3 "2022-09-17T11:06:50Z")
Hey,
> That is tricky as stem is not maintained anymore and therefore
> deprecated.
That is a pitty. It would be nice if you can actually make this obvious on the
git repo like "currently stem is unmaintained and therefore deprecated" and
maybe search for people in the community to take over - maybe ask people from
onionshare?
Especially as stem is still marked as the way to interact with tor via python.
Like it was done on this ml in August:
[https://lists.torproject.org/pipermail/tor-dev/2022-August/014768.html](https://lists.torproject.org/pipermail/tor-dev/2022-August/014768.html)
> There are no further releases planned and talking to atagar
> last time he said the master branch was not ready for release. We could
> think about minor point releases for the 1.8 series but those would just
> contain small bug fixes (like Python 3.10 compatibility) but no new
> features.
Having a way to work with Python 3.10+ is still great but will not help for
our use case as onionshare using the feature of client auth v3.
regards,
hefee
> **···**
>
> --
> Mein öffentlicher Schlüssel / My public key: E68031D299A6527C
> Fingerabdruck / Fingerprint:
> D256 4951 1272 8840 BB5E 99F2 E680 31D2 99A6 527C
> runterladen/download:
> [https://keys.openpgp.org/vks/v1/by-fingerprint/](https://keys.openpgp.org/vks/v1/by-fingerprint/)
> D256495112728840BB5E99F2E68031D299A6527C
---
### Author:  [@Damian\_Johnson](https://forum.torproject.org/u/Damian_Johnson)
#### Post date: [September 18, 2022, 7:40pm UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/4 "2022-09-18T19:40:59Z")
> \> That is tricky as stem is not maintained anymore and therefore
> \> deprecated.
>
> That is a pitty. It would be nice if you can actually make this obvious on the
> git repo like "currently stem is unmaintained and therefore deprecated"
Hiya. Just a minor terminology correction: Stem is unmaintained but
not deprecated. The later implies that there's a replacement. There's
other options [1] but for most of Stem's features it's the only game
in town.
> maybe search for people in the community to take over - maybe ask people from
> onionshare?
If someone's serious about it we can talk but properly maintaining
Stem is a lot of work [2][3].
> Especially as stem is still marked as the way to interact with tor via python.
As far as I'm aware it is.
Cheers! -Damian
[1] [Frequently Asked Questions — Stem 1.8.1-maint documentation](https://stem.torproject.org/faq.html#are-there-any-other-controller-libraries)
[2] [Spec compliance · Issue #97 · torproject/stem · GitHub](https://github.com/torproject/stem/issues/97)
[3] [Remove asyncio metaprogramming · Issue #77 · torproject/stem · GitHub](https://github.com/torproject/stem/issues/77)
> **···**
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> tor-dev mailing list
> tor-dev@lists.torproject.org
> [https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev)
---
### Author:  [@GeKo](https://forum.torproject.org/u/GeKo)
#### Post date: [September 19, 2022, 7:31am UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/5 "2022-09-19T07:31:22Z")
Hefee:
> Hey,
>
> > That is tricky as stem is not maintained anymore and therefore
> > deprecated.
>
> That is a pitty. It would be nice if you can actually make this obvious on the
> git repo like "currently stem is unmaintained and therefore deprecated" and
> maybe search for people in the community to take over - maybe ask people from
> onionshare?
We don't have access to the official repository on Github. We've had done it otherwise. For the taking over part it seems atagar replied already, great.
> Especially as stem is still marked as the way to interact with tor via python.
> Like it was done on this ml in August:
> [[tor-dev] TOR socket for P2P in Python](https://lists.torproject.org/pipermail/tor-dev/2022-August/014768.html)
>
> > There are no further releases planned ahttps://lists.torproject.org/pipermail/tor-dev/2022-August/014768.htmlnd talking to atagar
> > last time he said the master branch was not ready for release. We could
> > think about minor point releases for the 1.8 series but those would just
> > contain small bug fixes (like Python 3.10 compatibility) but no new
> > features.
>
> Having a way to work with Python 3.10+ is still great but will not help for
> our use case as onionshare using the feature of client auth v3.
That's right. atagar: what about this: it seems you already created a separate branch with the change needed by the onionshare folks (nice!). Would you mind creating a point release (or 1.9) so the Debian folks can pick that up, including the Python 3.10 compatibility fix as well? I think that would be the easiest short-term solution to the problem hefee came up with.
Thanks,
Georg
> **···**
>
> > regards,
> >
> > hefee
> >
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> > tor-dev mailing list
> > tor-dev@lists.torproject.org
> > [tor-dev Info Page](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev)
---
### Author:  [@meejah](https://forum.torproject.org/u/meejah)
#### Post date: [September 19, 2022, 4:38pm UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/6 "2022-09-19T16:38:38Z")
Hello,
A friendly reminder that txtorcon exists and supports v3 onions, (even if developed has slowed somewhat in recent times).
It probably doesn't help onionshare a lot, as txtorcon is a Twisted-based async API so it works best with other Twisted-using code.
That said, you \_can\_ inter-operate with asyncio or even with threaded code if you want. However, it's not going to be a drop-in Stem replacement (and that has never been txtorcon's goal).
[GitHub - meejah/txtorcon: Twisted-based asynchronous Tor control protocol implementation. Includes unit-tests, examples, state-tracking code and configuration abstraction.](https://github.com/meejah/txtorcon/)
Documentation available via onion (which self-hosts on the Twisted webserver with txtorcon for Tor support):
[http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/](http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/)
> **···**
>
> --
> meejah
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> tor-dev mailing list
> tor-dev@lists.torproject.org
> [https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev)
---
### Author:  [@juga](https://forum.torproject.org/u/juga)
#### Post date: [September 28, 2022, 5:31pm UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/7 "2022-09-28T17:31:30Z")
Hi hefee,
> > There are no further releases planned and talking to atagar
> > last time he said the master branch was not ready for release. We could
> > think about minor point releases for the 1.8 series but those would just
> > contain small bug fixes (like Python 3.10 compatibility) but no new
> > features.
>
> Having a way to work with Python 3.10+ is still great but will not help for
> our use case as onionshare using the feature of client auth v3.
we've released stem 1.8.1 [1] including v3 onion services patches [2]. There'd be a pypi package soon (in aprox. 1 day) and stem's website update.
Please, let us know whether that works for you,
Cheers,
juga.
[1] [Release 1.8.1 · torproject/stem · GitHub](https://github.com/torproject/stem/releases/tag/1.8.1)
[2] [Commits · torproject/stem · GitHub](https://github.com/torproject/stem/commits/maint)
> **···**
>
> On 9/17/22 11:06, Hefee wrote:
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> tor-dev mailing list
> tor-dev@lists.torproject.org
> [https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev)
---
### Author:  [@Hefee](https://forum.torproject.org/u/Hefee)
#### Post date: [October 3, 2022, 12:05am UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/8 "2022-10-03T00:05:22Z")
Hi hefee,
> we've released stem 1.8.1 [1] including v3 onion services patches [2].
> There'd be a pypi package soon (in aprox. 1 day) and stem's website update.
>
> Please, let us know whether that works for you,
Thanks a lot. It looks fine for our use case. And good that you now communicate
it openly that there is active development for the moment.
Regards,
hefee
---
### Author:  [@GeKo](https://forum.torproject.org/u/GeKo)
#### Post date: [October 3, 2022, 7:10am UTC](https://forum.torproject.org/t/tor-dev-release-new-version-of-stem/4551/9 "2022-10-03T07:10:31Z")
Hefee:
> Hi hefee,
>
> > we've released stem 1.8.1 [1] including v3 onion services patches [2].
> > There'd be a pypi package soon (in aprox. 1 day) and stem's website update.
> >
> > Please, let us know whether that works for you,
>
> Thanks a lot. It looks fine for our use case. And good that you now communicate
> it openly that there is active development for the moment.
Just to get that part less confusing for others following along: I guess you meant that there is \*no\* active development at the moment, which is right. 🙂
Georg
> **···**
>
> > Regards,
> >
> > hefee
> >
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> > tor-dev mailing list
> > tor-dev@lists.torproject.org
> > [tor-dev Info Page](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev)