Florian Schulze added the comment:
You are right, this actually happens with Python 2.7.14 as well. I was fooled
by a warnings.filterwarnings matching to a path in my codebase. That one did
match for my Python 2.7.15 testing but didn't for my Python 2.7.14 testing,
because those were do
Florian Schulze added the comment:
Yes, it's third party code, but that worked up until Python 2.7.14 and only
broke with 2.7.15, which is why I reported it here.
The expected behaviour is not a SyntaxError, but a DeprecationWarning, which is
what you get pre Python 2.7.15. So this
New submission from Florian Schulze :
Since Python 2.7.15 import bs4 (BeautifulSoup4) fails when using the -3 option
on the Python binary.
...
'You are trying to run the Python 2 version of Beautiful Soup under Python
3. This will not work.'<>'You need to conver
Florian Schulze added the comment:
Due to the TLS changes on pypi.org the buildout I used before doesn't work
anymore on Travis and I have now switched to pyenv. If I ever stumble over it
again, I will open a new bug with more information.
--
stage: -> resolved
stat
New submission from Florian Schulze :
While the tests run there is a segfault:
https://travis-ci.org/collective/buildout.python/jobs/360190312#L2529
Started with b2 and still happens in b3, b1 built fine.
--
components: Build, Tests
messages: 314767
nosy: fschulze
priority: normal
Florian Schulze added the comment:
The documentation patch is a definite improvement.
--
nosy: +fschulze
___
Python tracker
<http://bugs.python.org/issue8
Florian Schulze added the comment:
Ok, I reread
https://docs.python.org/3/library/sqlite3.html#controlling-transactions several
times now. I think it's confusing.
I want explicit transaction handling, but ``isolation_level = None`` turns on
"autocommit mode". Unfortunate
Florian Schulze added the comment:
How do we proceed from here? The Python 3.6.0rc1 is looming. If this is a bug
in sqlite, then we need a workaround. We can't wait for a fix in sqlite,
because it's not bundled with Python and without the fix Python 3.6 breaks with
older sqlite ver
New submission from Florian Schulze:
Using:
conn = sqlite3.connect(':memory:', isolation_level='IMMEDIATE')
conn.execute('begin immediate')
Throws:
sqlite3.OperationalError: cannot start a transaction within a transaction
This didn't happen in previous v
