Michal Plichta
Michal Plichta
Had same issue see my last 2 comments here: #111 (workaround)
I would love to handle those, but @charliefoxtwo I need some support to understand issue and you idea to fix it
Got it... anyway I will try, will post my findings here... or I will open PR with proposed solution for both #1017 and #1033
It looks to me **appveyor** is kind of redundant (and slow), but I leave decision to you what to do with it. Changes are working in my fork and producing...
Yeah, `setuptools!=72.0.0` I've tried this and it doesn't work. Do not remember, but I think I try `setuptools==72.1.0` as well and it didn't work.
@scoder Looks like **AppVeyor** job is passing but **doctest of README.rst** not! Not sure it is related to newest `setuptools` since we block only `72.0.0`, but with `setuptools
From logs, there is problem with importing `lua54` but job is passing. ``` python -u -m lupa.tests.__main__ test (unittest.loader._FailedTest) ... ERROR C:\projects\lupa\lupa\tests\..\..\README.rst Doctest: README.rst ... FAIL ====================================================================== ERROR: test (unittest.loader._FailedTest)...