Re: [Twisted-Python] Python3: should paths be bytes or str?

2014-09-08 Thread Wolfgang Rohdewald
Am Montag, 8. September 2014, 02:14:10 schrieb exar...@twistedmatrix.com: > On 01:26 am, wolfgang@rohdewald.de wrote: > >The porting guide says > > > >No byte paths in sys.path. > > What porting guide is that? https://twistedmatrix.com/trac/wiki/Plan/Python3 see the reviewer check list > it

[Twisted-Python] PEP3131: non-ascii identifiers

2014-09-08 Thread Wolfgang Rohdewald
This does not seem to be supported by Python yet. Should that be enabled at all? If one process with PY3 sends such identifiers to a separate process with PY2, that will fail. I am not sure if that would be a problem, whoever uses this must make sure PY3 is used everywhere. If this should be for

Re: [Twisted-Python] Python3: should paths be bytes or str?

2014-09-08 Thread anatoly techtonik
On Mon, Sep 8, 2014 at 5:14 AM, wrote: > On 01:26 am, wolfgang@rohdewald.de wrote: >> >> The porting guide says >> >> No byte paths in sys.path. > > > What porting guide is that? >> >> >> doc for FilePath says >>On both Python 2 and Python 3, paths can only be bytes. >> >> >> I stumbled u

Re: [Twisted-Python] PEP3131: non-ascii identifiers

2014-09-08 Thread exarkun
On 09:19 am, wolfgang@rohdewald.de wrote: This does not seem to be supported by Python yet. Should that be enabled at all? If one process with PY3 sends such identifiers to a separate process with PY2, that will fail. I am not sure if that would be a problem, whoever uses this must make sure

Re: [Twisted-Python] PEP3131: non-ascii identifiers

2014-09-08 Thread Wolfgang Rohdewald
Am Montag, 8. September 2014, 10:54:44 schrieb exar...@twistedmatrix.com: > Can you point out the specific places where you think PB needs to start > using UTF-8 instead of ASCII? Those are the places that need to be > fixed, not the underlying porting helpers they happen to use. My question is

Re: [Twisted-Python] PEP3131: non-ascii identifiers

2014-09-08 Thread exarkun
On 11:44 am, wolfgang@rohdewald.de wrote: Am Montag, 8. September 2014, 10:54:44 schrieb exar...@twistedmatrix.com: Can you point out the specific places where you think PB needs to start using UTF-8 instead of ASCII? Those are the places that need to be fixed, not the underlying porting h

Re: [Twisted-Python] PEP3131: non-ascii identifiers

2014-09-08 Thread Wolfgang Rohdewald
Am Montag, 8. September 2014, 12:04:46 schrieb exar...@twistedmatrix.com: > PB supports unicode perfectly well and has for many years. This is why > I asked which specific part of PB has a problem. PB transfers names of methods and classes as bytes, not as unicode. Which is logical since PY2 doe

Re: [Twisted-Python] PEP3131: non-ascii identifiers

2014-09-08 Thread exarkun
On 01:07 pm, wolfgang@rohdewald.de wrote: Am Montag, 8. September 2014, 12:04:46 schrieb exar...@twistedmatrix.com: PB supports unicode perfectly well and has for many years. This is why I asked which specific part of PB has a problem. PB transfers names of methods and classes as bytes,

Re: [Twisted-Python] pb.Copyable knowledge barrier

2014-09-08 Thread Kevin Mcintyre
Jelly performance factors below expectations. I am not clear on the significance of this statement. Not significant, just an observation. I've made this statement before, backed-off after finding errors on my code, but after fixing I see performance across the bus that still seem slow. "Seem s

Re: [Twisted-Python] Python3: should paths be bytes or str?

2014-09-08 Thread Glyph
On Sep 7, 2014, at 7:14 PM, exar...@twistedmatrix.com wrote: > On 01:26 am, wolfgang@rohdewald.de wrote: >> The porting guide says >> >> No byte paths in sys.path. > > What porting guide is that? >> >> doc for FilePath says >> On both Python 2 and Python 3, paths can only be bytes. >> >