ERPNext + Python 3

Please see PR fix: smtp rfc compliance and line endings for exchange 2016/RFC email servers. by cjpit · Pull Request #8708 · frappe/frappe · GitHub - Give it a test and let me know if that fixes the issue…

this worked for me

I tried all the above but failed to updgrade … Please help

here is the error on bench migrate-env python3
DEBUG:bench.commands:Clearing Redis Cache…
INFO:bench.utils:/usr/local/bin/redis-cli -p 13000 FLUSHALL
OK
DEBUG:bench.commands:Clearing Redis DataBase…
INFO:bench.utils:/usr/local/bin/redis-cli -p 13000 FLUSHDB
OK
DEBUG:bench.commands:Backing up Virtual Environment
DEBUG:bench.commands:Migration Error
Traceback (most recent call last):
File “/home/erpnext/.local/bin/bench”, line 11, in
load_entry_point(‘bench’, ‘console_scripts’, ‘bench’)()
File “/opt/erpnext/bench-repo/bench/cli.py”, line 40, in cli
bench_command()
File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 764, in call
return self.main(*args, **kwargs)
File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 717, in main
rv = self.invoke(ctx)
File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 555, in invoke
return callback(*args, **kwargs)
File “/opt/erpnext/bench-repo/bench/commands/init.py”, line 142, in migrate_env
os.rename(source, dest)
OSError: [Errno 2] No such file or directory

1 Like

Hi @asoral

Did you get a solution to this? Just encountered same issue

Kind regards,

You may need to pass a path to bench migrate-env:

   $ which python3
   /usr/bin/python3
   $ bench migrate-env /usr/bin/python3
1 Like

Hi @tmatteson

Thanks for the response. I actually found out the env folder was gone! Had to copy over the most recent from the archived_envs folder and looks like that solved the migration issue. I’m however now trying to resolve the good ol’ “Sorry! We will be back soon” issue

Cheers