my personal opinion: as long as there are no security concerns (e.g. it still works with the current python version) I don't see a problem in using software that is no longer actively developed. I would think it would still make an interesting article.
My pleasure. I think it's a very nice idea to give a shout out to the software we like.
I, for example, quite often use [`expex`](https://ctan.org/pkg/expex) which is a very old package. Last release was around 8 years ago, but till date, its output is unmatched with that of other similar packages.
Why not if you think it is a good package? Some of the inactive projects are really good and stable.
@samcarter @skillmon ^^^ I think it's not the case to write an article on it if it's inactive. Or do you think it might still be worth it?
The maintainer replied: "That project is pretty inactive. It's not completely unmaintained though. If something is broken on e.g. a new Python version I'll fix it. But there's no new features planned. It's fairly complete though in my opinion, so you can still use it."
I think there's a word missing in that sentence, I don't fully grasp what you're trying to say ("I don't you").
I found it very nice, it allows much faster compilation of your document because you can create all your plots parallelised and they integrate into your document absolutely seamless.
Yes, of course! I'll take it into account for one of the next articles
I didn't reach the author, I'll try but I don't know if I get an answer at once
you could also cover direct plot generation via `matplotlib`'s `pgf` backend. I did all my plots that way when I was in university.
Last commit 6 months ago, last release 1 year 3 months ago, but the release before that was in 2020. One could say that development at least slowed down a lot, but maybe it's just stable enough for the authors' needs? Did you try reaching the authors/maintainers?
Does the Professor already have alternative ideas or would he like a community brainstorming for possible topics?
Prof. van Duck would have liked to write an article about PyLaTeX but he has just find out this: "We found indications that PyLaTeX is an Inactive project." Quack in despair!
Thanks to everyone who voted for/against the tophat for the snowman cookie cutter! Given the tie of stars (:star::star: each), I decided to follow @Skillmon's argument for a simpler shape and move the tophatted snowman to a separate branch.
Welcome on the other side! There is also the possibility to import a question from TeX.SX (though that only makes sense if you also provide answers).
The source of the calendar is also public at https://github.com/TikZlings/Extravaganza2024/tree/main/calendar in case you'd like to see which modifications etc. we made
The calendar was made using LianTze Lim's fantastic calendar template https://tex.my/category/calendar/
Welcome to TopAnswers/TeX! It would be nice if the new question would be understandable on its own, but you can always add a link back to the question on tex.se if necessary for context.
By the way, that calendar is beautiful. Was it made with a latex package?
Is it inappropriate to ask questions which are follow ups on old stackexchange questions here?
You should be able to read the answer now. Thanks again! (I kept the text that triggers the bug in case it is needed by Jack, but it is certainly still in the answer history, first revision).
The answer is “ready” now (I kept the original in case Jack wants to debug the problem; I think it was not in the `\directlua` paragraph, rather where whatsits are presented). It's a bit long, but helpful I hope...
There are a few things that I already corrected locally in my draft, so what there is on site is not ready yet, thanks! :-)