Further debugging - using the python3.6 from the virtual environment where mailman is running, it looks like it is trying to use utf-8:
import locale import codecs print(locale.getpreferredencoding()) UTF-8 print(codecs.lookup(locale.getpreferredencoding()).name) utf-8
Thoughts?
On Mon, Apr 16, 2018 at 11:29 AM, Darren Smith <silas.crutherton@gmail.com> wrote:
By the way, in reading the URL in the error, I attempted to set the LANG and LC_ALL to en_US.utf8 (as was found in the error) but it still does not work.
On Mon, Apr 16, 2018 at 11:26 AM, Darren Smith <silas.crutherton@gmail.com
wrote:
Nice...spoke too soon.
Mailman info works, but when attempting to start mailman I'm now getting this:
Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 676, in main _verify_python3_env() File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps.
This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion others)
-Darren
On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith < silas.crutherton@gmail.com> wrote:
Boy howdy did that work...
Thanks!
On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/16/2018 10:12 AM, Darren Smith wrote:
"/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components."
Anyone able to point me where to go to look for a solution for this?
You need to update SQLAlchemy to >= 1.2 for this, but there is another issue that requires at least 1.2.3 (current is 1.2.6)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/