RjOllos <rjol...@gmail.com> writes: >> Trac 1.0 is documented not to support python 3, and the package notes >> this in a comment. Still true? > > There is still not support for Python 3. Python 3 support may be coming > with Trac 1.3.x.
Thanks. I didn't mean to complain -- more that I was checking that I was not confused. >> The package supports sqlite3 and pgsql via pyscopg2. I use pgsql. >> The package notes that mysql is not recommended by upstream. Is that >> still a fair statement? > > I can see why MySQL was not recommended at one time, but support is pretty > good now so I think you could remove that statement. OK - I have softened it: # Upstream has MySQL support but there are significant caveats: # https://trac.edgewall.org/wiki/MySqlDb # Anyone is welcome to add a (tested!) mysql option. The bit about charsets scares me slightly, so I'm leaving it for someone who wants to run it to test on NetBSD. I find that pgsql works great (and has for a really long time), so I'm personally sticking with it. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
