Re: [Python-Dev] Pydoc Replacement for Python's help()?

2015-01-28 Thread Chris Barker - NOAA Federal
Just want to make sure you're aware of the new mobile-sig: https://mail.python.org/mailman/listinfo/mobile-sig No need to do this on your own. -Chris > On Jan 27, 2015, at 4:21 PM, Cyd Haselton wrote: > >> On Tue, Jan 27, 2015 at 2:45 PM, Glenn Linderman >> wrote: >> On 1/27/2015 8:04 AM, Cy

Re: [Python-Dev] also

2015-01-28 Thread Steven D'Aprano
On Wed, Jan 28, 2015 at 09:39:25AM -0500, Alan Armour wrote: > if you can do this > > a chemical physics and element physics like everything from melting points > to how much heat you need to add two chemicals together > > and physics like aerodynamics, space dynamics, and hydrodynamics etcet

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-01-28 Thread Cyd Haselton
That is interesting.../dev/__properties__ is in memory...not the filesystem, apparently proccesses read global properties from it. It's read-only...not sure why the build or the python binary would access it...or if that's the cause of the segfault. I have root access on the tablet so I was able t

Re: [Python-Dev] Why co_names? Wouldn't be simpler to just use co_consts?

2015-01-28 Thread Andrea Griffini
The names stored in op_names are totally unrelated as they can be attribute names, module names, global names; you basically don't know much about them unless you also inspect the actual bytecode using them (and the same name can be used in completely different ways in different parts of the same c

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-01-28 Thread Ryan Gonzalez
On Wed, Jan 28, 2015 at 10:43 AM, Guido van Rossum wrote: > What I see in the strace: > > ... load libpython3.4m.so.1.0 > ... load libm > ... open /dev/__properties__ and do something to it (what?) > ... get current time > ... allocate memory > ... getuid > ... segfault > > That's not a lot to go

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-01-28 Thread Cyd Haselton
Apologies...I'm not sure what a stack track is, but I do have the strace. Nearest I can tell, it happens due to an open call, though I am probably wrong. Attaching the strace output to this email. I'm going to head back to the documentation and to back out of some Android-related changes in _loca

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-01-28 Thread Guido van Rossum
What I see in the strace: ... load libpython3.4m.so.1.0 ... load libm ... open /dev/__properties__ and do something to it (what?) ... get current time ... allocate memory ... getuid ... segfault That's not a lot to go on, but it doesn't look as if it has started to load modules yet. Does /dev/__

Re: [Python-Dev] also

2015-01-28 Thread MRAB
On 2015-01-28 14:39, Alan Armour wrote: if you can do this a chemical physics and element physics like everything from melting points to how much heat you need to add two chemicals together and physics like aerodynamics, space dynamics, and hydrodynamics etcetera for propellers and motors a

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-01-28 Thread Guido van Rossum
There could be a million differences relevant (unicode, ints, ...). Perhaps the importlib bootstrap is failing. Perhaps the dynamic loading code changed. Did you get a stack track? (IIRC strace shows a syscall trace -- also useful, but doesn't tell you precisely how it segfaulted.) On Wed, Jan 28,

Re: [Python-Dev] also

2015-01-28 Thread Brett Cannon
You have the wrong mailing list for this sort of request. This is list is about the development *of* Python, not *with* it. And since Python the language is not in the business of providing libraries for such specific needs this kind of request isn't appropriate here. You can try asking somewhere l

[Python-Dev] also

2015-01-28 Thread Alan Armour
if you can do this a chemical physics and element physics like everything from melting points to how much heat you need to add two chemicals together and physics like aerodynamics, space dynamics, and hydrodynamics etcetera for propellers and motors and stuff. just having this in a main lang

Re: [Python-Dev] development

2015-01-28 Thread Brian Curtin
On Wednesday, January 28, 2015, Alan Armour wrote: > can you guys develop an audio kit that works around jackd or on windows > directx? and tutorials to write synthesizers. and drum machines like a > tr-606 with triggers ( I want to trigger a drum synth like the March > UDS(Soviet) Coolest d

[Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-01-28 Thread Cyd Haselton
All, I recently ditched my attempts to port Python 2.7.8 to Android in favor of Python 3.4.2. Unfortunately, after using the same configure options in the same environment, and modifying the setup.py as needed, the newly built binary throws a segfault when the generate-posix-vars portion of the bu

[Python-Dev] development

2015-01-28 Thread Alan Armour
can you guys develop an audio kit that works around jackd or on windows directx? and tutorials to write synthesizers. and drum machines like a tr-606 with triggers ( I want to trigger a drum synth like the March UDS(Soviet) Coolest drum synth EVER. Also, I think you should have a way to writ

Re: [Python-Dev] Why co_names? Wouldn't be simpler to just use co_consts?

2015-01-28 Thread Nick Coghlan
On 28 January 2015 at 21:21, Greg Ewing wrote: > Andrea Griffini wrote: >> >> Sorry if the question is naive, but why is co_names needed? Wouldn't be >> simpler to just use co_consts? > > One reason might be that keeping them separate means > you can have up to 256 names and 256 consts using > 1-b

Re: [Python-Dev] Why co_names? Wouldn't be simpler to just use co_consts?

2015-01-28 Thread Greg Ewing
Andrea Griffini wrote: Sorry if the question is naive, but why is co_names needed? Wouldn't be simpler to just use co_consts? One reason might be that keeping them separate means you can have up to 256 names and 256 consts using 1-byte opcode arguments. Otherwise, you'd be limited to a total of

Re: [Python-Dev] PEP 468 (Ordered kwargs)

2015-01-28 Thread Chris Withers
On 28/01/2015 07:14, Gregory P. Smith wrote: It is a potentially bad idea if order is the default behavior of iteration, items(), keys() and values(). Ideally order should only be exposed when explicitly asked for to help prevent bugs and mitigate potential information leaks. I have to be hone

[Python-Dev] Why co_names? Wouldn't be simpler to just use co_consts?

2015-01-28 Thread Andrea Griffini
Sorry if the question is naive, but why is co_names needed? Wouldn't be simpler to just use co_consts? Andrea ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mail