SQLAlchemy custom test configuration file as $XDG_CONFIG_HOME/satest.cfg?

[Priit Laes]

It seems like a good time (for 0.8) to move the custom test configuration from ~/.satest.cfg to ~/.config/satest.cfg. Mainly because it declutters the home dir and ~/.config is becoming de-facto default directory for configuration files.

A bit more extreme step would be looking up user's configuration directory using {{{$XDG_CONFIG_HOME}}} env variable: http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html

[Mike Bayer]

i don't even get the use case for ~/.satest.cfg, I was going to remove it. setup.cfg in the local install is the primary config for tests (I'm moving things to check for db there first) and we also check "test.cfg" as a local-file fallback.

do you have a use case to run the actual SQLAlchemy unit tests in various locations while all reading from a home-directory file ?

[Mike Bayer]

also regarding testing I'm hand-wringing a bit how to test third-party dialects. I've started building a whole new test suite within SQLAlchemy itself, I considered having it as a separate download but I'd like SQLA itself to use it for its own tests.

https://bitbucket.org/zzzeek/sqla_including_suite/src/40fd1997f0740b0111c4d7dabe06b73c1122ba4d/lib/sqlalchemy/testing/suite

my concern is it makes SQLAlchemy installations that much bigger.

[Priit Laes]

Replying to zzzeek:

do you have a use case to run the actual SQLAlchemy unit tests in various locations while all reading from a home-directory file ?

Nope, no real testcase (as I'm only playing around with pgsql), but I saw it in a commit diff and though I would just raise the issue about moving it to proper place.

also regarding testing I'm hand-wringing a bit how to test third-party dialects. I've started building a whole new test suite within SQLAlchemy itself, I considered having it as a separate download but I'd like SQLA itself to use it for its own tests.

Maybe leave that for 0.9? :P

[Mike Bayer]

ah unlikely as I'm doing a third-party dialect for a client. its essentially just a move of .py files for now and wont really be noticeable to anyone other than the bigger install size.

[Mike Bayer]

anyway the .satest.cfg is removed from the current 0.8 tip.