New submission from Tristan :
>From Python 3.7, sre_parse.parse() do not create SubPattern instances that can
>be used to back reproduce original expression if containing non-capturing
>groups.
In Python 3.6:
>>> import sre_parse
>>> sre_parse.parse("
Tristan Colombo <tristan.colo...@gmail.com> added the comment:
Running on Debian Etch
Ok, my python3 was broken and links to python3.5.3
All my apologizes
--
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@
Tristan Colombo <tristan.colo...@gmail.com> added the comment:
Correction of my previous correction :
server = socketserver.TCPServer((HOST, PORT), MyTCPHandler)
'with' statement can not be used...
--
___
Python tracker <rep...@bugs.p
New submission from Tristan Colombo <tristan.colo...@gmail.com>:
In the documentation, at page :
- https://docs.python.org/3.6/library/socketserver.html
- Section 21.21.4.1
In the server side code :
if __name__ == "__main__":
HOST, PORT = "localhost",
#
Tristan Croll added the comment:
I've cross-posted the following to the SWIG bug tracker. Hopefully someone can
find an answer, because I'm getting nowhere.
If I have two classes Foo and Bar (where Bar has a function get_foo() that
returns a Foo object) defined in the SWIG-generated library
Tristan Croll added the comment:
I don't agree that it should be closed yet. I still have the issue that an
approach that was perfectly legal in Python 3.5 now no longer works in Python
3.6, and I don't know why. The description in msg289281 stands, and is a real
problem. Nothing has changed
Tristan Croll added the comment:
Sorry - ignore that. Brain-fart at the end of a (very) long day.
--
versions: -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Tristan Croll added the comment:
Nope - belay that. Checking through the SWIG-generated Python code, all the
classes correctly inherit from object, which negates that issue.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Tristan Croll added the comment:
OK, this seems to narrow down the problem. The following was legal in Python
3.5.1, but in 3.5.3 and 3.6.1rc1 returns:
'TypeError: must be type, not classobj'
class Foo_Base:
pass
class Bar_Base:
def get_foo(self):
f = Foo_Base
Tristan Croll added the comment:
OK, a further clue. First, a little more detail on how my project is arranged
(to re-iterate, this works without complaint in Python 3.5):
Rather than use my SWIG output directly, I've created a further wrapper layer
in Python to add functions/syntactic sugar
New submission from Tristan Croll:
Possibly related to http://bugs.python.org/issue29327 - yields the same error
message:
Objects/tupleobject.c:81: bad argument to internal function
I have a large SWIG project which was previously working well in Python 3.5.
After migrating to Python 3.6.0
Changes by Tristan Fisher <tristan.fis...@gmail.com>:
--
nosy: +Tristan.Fisher
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pytho
New submission from Tristan Fisher:
It's my understanding that giving the action=store_true to an argument in
argparse defaults to False. When using non-double-dashed/positional arguments,
the argument resorts to True (even if explicitly marked default=False).
I've attached a minimal example
Tristan Carel tristan.ca...@gmail.com added the comment:
I have experienced the same problem under ppc64 aix 6.1.2.0 while compiling
Python 2.7.1
$ cd Python-2.7.1
$ mkdir __build
$ cd __build
$ ../configure --with-gcc=xlc_r --with-cxx-main=xlC_r --with-threads
--disable-ipv6
$ /usr/linux/bin
14 matches
Mail list logo
