It would be indeed nice if I created a PyPI for it. I think when the projects got forked from the beancount repo I never did that.
On Tue, May 28, 2024 at 11:19 PM Red S <[email protected]> wrote: > Not releases, but just a single release would suffice. > > The first release implies the author/maintainer deemed it release-worthy, > which is meaningful when viewed in the context of the reputation of the > author/maintainer. This message > <https://groups.google.com/g/beancount/c/c_NwZGbgOXo/m/qYX-qEtsBAAJ> > explicitly says it’s not ready for a release, and that being a strong > warning. Fair enough if that’s the state of it, but that may also > reasonably interpreted to mean one shouldn’t be coding and releasing other > software against it. Plus, a release would result in a PyPI package > presumably, which is also required for other packages to depend on it. > > Regular releases/commits help signify activity, and are not an ask, at > least from me here. > > Does that help clarify? > > > On Tuesday, May 28, 2024 at 7:58:38 PM UTC-7 [email protected] wrote: > > I mean it does the job, should we make releases just so people feel like > it's changing? > I can commit a diff every month on the readme file if it helps /shrug > > > On Tue, May 28, 2024, 01:29 Red S <[email protected]> wrote: > > > > On Monday, May 27, 2024 at 7:32:52 PM UTC-7 [email protected] wrote: > > On Wednesday, May 22, 2024 at 9:59:14 AM UTC+7 Red S wrote: > > Mini rant: I’d love for anyone who writes an importer to come to the same > realization Felipe did, and *write it using the beangulp API*. > > > I have several written several importers. I've never looked at moving them > to beangulp. Because when I look at beangulp's github repository there are > no releases, no commits in 8 months, and the "Status" documentation says > "As of February 2021, the project has just been forked out of Beancount. > Expect some changes to be made here." > > I assume, perhaps incorrectly(?), that if beangulp isn't in a state to be > released yet then it isn't in a state for me to migrate my importers to it. > > > I’ve done the same thing for exactly the same reasons, and thus, > beancount_reds_importers > <https://github.com/redstreet/beancount_reds_importers> is written > against bean-{identify, extract, file} in Beancount v2 instead of beangulp. > Good catch, thank you, I should’ve been more explicit and instead > recommended that people write importers against released code, which in > this case is Beancount v2’s importers. > > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/7332b74a-39c8-476d-83dd-9dae2ed7c864n%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/7332b74a-39c8-476d-83dd-9dae2ed7c864n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhP0pW7pxyq4yO%3DxWt_JkffaF3g8k-NTG9bJkiSZzZzqsQ%40mail.gmail.com.
