Stuart Henderson - Thu, 10 March 2022 at 12:54:12
> The difference is that other ports of standalone software are using
> flask. (onionshare, puppetboard etc)
yes, and there were no django based apps in ports...
system packages are fine until all software runs on the same pinned
flask version.
On 2022/03/10 11:55, f.holop wrote:
> Ricardo - Sat, 26 February 2022 at 02:24:20
> > I just noticed that our version of www/py-flask and its dependencies
> > are ancient. Current flask version is from almost 4 years ago, even
> > though the project released 2.0.0 a couple of months ago and stills
Ricardo - Sat, 26 February 2022 at 02:24:20
> I just noticed that our version of www/py-flask and its dependencies
> are ancient. Current flask version is from almost 4 years ago, even
> though the project released 2.0.0 a couple of months ago and stills
> active maintain it.
i'll say the same
On 2022/03/04 19:33, Ricardo wrote:
> Hey sthen@,
>
> Took your suggestions (always good ones. Thanks) and waited for py-test to be
> updated.
> Both py-flask (make test [OK]) and py-werkzeug (make test only shows an error
> with test_reloader_sys_path[watchdog] and
>
On 2022/02/26 10:11, Stuart Henderson wrote:
> On 2022/02/26 02:24, Ricardo wrote:
> > However, currently I'm stuck with www/py-werkzeug and www/py-flask on
> > make test. Everything else seems to be working, but I'm getting these
> > errors respectively:
>
> I haven't checked for sure but it is
On 2022/02/26 02:24, Ricardo wrote:
> However, currently I'm stuck with www/py-werkzeug and www/py-flask on
> make test. Everything else seems to be working, but I'm getting these
> errors respectively:
I haven't checked for sure but it is quite likely that they require
newer py-test and friends,
