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

[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/mailman/options/python-dev/archive%40mail-archive.com

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

[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 honest, I think that's the opposite of most new users 
assumption...



Experience cleaning up our huge code base at work to turn on hash
randomization by default a couple years ago has shown that people depend
on iteration order in code often without intending to. This often leads
to latent bugs. Keep iteration order unstable by default and you prevent
people from doing that.


Hmm, well, or you could say that always having ordering would mean the 
behaviour would match new users experimental understanding and so 
eliminate all bugs that occur when people accidentally rely on ordering.


Personally, I'd prefer to see us be explicit about data structures used 
when "security matters", an explicit RandomOrderedDict would make that 
clear.


cheers,

Chris
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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 256 of both.

--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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-byte opcode arguments. Otherwise, you'd be limited
> to a total of 256 of both.

They're logically distinct things accessed by different opcodes for
very different purposes. While you theoretically *could* use one array
to hold both, it would make the eval code harder to read, and various
introspection tasks (like "tell me all the names referenced from this
code object") significantly more difficult.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] development

[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 write assembler functions to really
optimize speed and have a table and stuff for assembler learning for all
cpus and stuff. even asm graphics and audio would be super useful in some
instances.



Thanks for your time
-Ty
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Newly Built Python3 Binary Throws Segfault

[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 build is reached...and when it is run as well (i.e.
./python --help, ./python -E -S -m sysconfig, or similar)

I took a strace of ./python, however I'm a bit lost when reviewing it.
Any ideas as to what may be going on...i.e. why Python 2.7 works but
3.x throws a segfault?

Thanks in advance,
Cyd
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] development

[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 drum synth EVER.
>
>
> Also, I think you should have a way to write assembler functions to really
> optimize speed and have a table and stuff for assembler learning for all
> cpus and stuff. even asm graphics and audio would be super useful in some
> instances.
>

That's not how this works.

If you would like to write all of that code and allow it to mature in the
wild while building a following around it and ensuring it is the best of
its kind and a general enough solution to be included in the Python
standard library, inclusion of that could be discussed in the future.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] also

[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 language seems to make a shit ton of sense.


Just like all the physics you can think of from electrical equipment to
building microchips to oscillators and resistors and stuff like that.

thanks
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] also

[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 like python-list to see if a library already exists for your
needs, though.

On Wed Jan 28 2015 at 10:13:03 AM 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 and stuff.
>
> just having this in a main language seems to make a shit ton of sense.
>
>
> Just like all the physics you can think of from electrical equipment to
> building microchips to oscillators and resistors and stuff like that.
>
> thanks
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
> brett%40python.org
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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, 2015 at 6:43 AM, Cyd Haselton  wrote:

> 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 build is reached...and when it is run as well (i.e.
> ./python --help, ./python -E -S -m sysconfig, or similar)
>
> I took a strace of ./python, however I'm a bit lost when reviewing it.
> Any ideas as to what may be going on...i.e. why Python 2.7 works but
> 3.x throws a segfault?
>
> Thanks in advance,
> Cyd
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>



-- 
--Guido van Rossum (python.org/~guido)
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] also

[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 and stuff.

just having this in a main language seems to make a shit ton of sense.


Just like all the physics you can think of from electrical equipment to
building microchips to oscillators and resistors and stuff like that.

thanks


You should be looking at Wolfram Alpha instead...
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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/__properties__ ring a bell? Not to me.

That stack trace would be really helpful.

On Wed, Jan 28, 2015 at 8:34 AM, Cyd Haselton  wrote:

> 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
> _localemodule.c
>
> On Wed, Jan 28, 2015 at 9:43 AM, Guido van Rossum 
> wrote:
> > 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, 2015 at 6:43 AM, Cyd Haselton 
> wrote:
> >>
> >> 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 build is reached...and when it is run as well (i.e.
> >> ./python --help, ./python -E -S -m sysconfig, or similar)
> >>
> >> I took a strace of ./python, however I'm a bit lost when reviewing it.
> >> Any ideas as to what may be going on...i.e. why Python 2.7 works but
> >> 3.x throws a segfault?
> >>
> >> Thanks in advance,
> >> Cyd
> >> ___
> >> Python-Dev mailing list
> >> Python-Dev@python.org
> >> https://mail.python.org/mailman/listinfo/python-dev
> >> Unsubscribe:
> >> https://mail.python.org/mailman/options/python-dev/guido%40python.org
> >
> >
> >
> >
> > --
> > --Guido van Rossum (python.org/~guido)
>



-- 
--Guido van Rossum (python.org/~guido)
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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
_localemodule.c

On Wed, Jan 28, 2015 at 9:43 AM, Guido van Rossum  wrote:
> 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, 2015 at 6:43 AM, Cyd Haselton  wrote:
>>
>> 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 build is reached...and when it is run as well (i.e.
>> ./python --help, ./python -E -S -m sysconfig, or similar)
>>
>> I took a strace of ./python, however I'm a bit lost when reviewing it.
>> Any ideas as to what may be going on...i.e. why Python 2.7 works but
>> 3.x throws a segfault?
>>
>> Thanks in advance,
>> Cyd
>> ___
>> Python-Dev mailing list
>> Python-Dev@python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe:
>> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>
>
>
>
> --
> --Guido van Rossum (python.org/~guido)


sout
Description: Binary data
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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 on, but it doesn't look as if it has started to
> load modules yet.
>
> Does /dev/__properties__ ring a bell? Not to me.
>
>
https://android.googlesource.com/platform/system/core/+/tools_r22/init/property_service.c
is the code that works with that file.

This

explains
it a bit (slides 24-29). Looks like something to do with interprocess
communication. Likely has nothing to do with Python itself.

Maybe this

would
be useful?


> That stack trace would be really helpful.
>
> On Wed, Jan 28, 2015 at 8:34 AM, Cyd Haselton  wrote:
>
>> 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
>> _localemodule.c
>>
>> On Wed, Jan 28, 2015 at 9:43 AM, Guido van Rossum 
>> wrote:
>> > 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, 2015 at 6:43 AM, Cyd Haselton 
>> wrote:
>> >>
>> >> 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 build is reached...and when it is run as well (i.e.
>> >> ./python --help, ./python -E -S -m sysconfig, or similar)
>> >>
>> >> I took a strace of ./python, however I'm a bit lost when reviewing it.
>> >> Any ideas as to what may be going on...i.e. why Python 2.7 works but
>> >> 3.x throws a segfault?
>> >>
>> >> Thanks in advance,
>> >> Cyd
>> >> ___
>> >> Python-Dev mailing list
>> >> Python-Dev@python.org
>> >> https://mail.python.org/mailman/listinfo/python-dev
>> >> Unsubscribe:
>> >> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>> >
>> >
>> >
>> >
>> > --
>> > --Guido van Rossum (python.org/~guido)
>>
>
>
>
> --
> --Guido van Rossum (python.org/~guido)
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com
>
>


-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
"It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated."
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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
code object). In my opinion introspection code telling me that the name
`foo` is used but not knowing if it's about a global, a module name or an
attribute name is not going to be that useful, on the other hand if you do
inspect the bytecode then using co_consts doesn't make things more
complicate.

Anyway I was just curious to know if there was any technical reason (that I
couldn't see) or if it was more a style/historic reason.

Thank you for the clarification

On Wed, Jan 28, 2015 at 1:40 PM, Nick Coghlan  wrote:

> 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-byte opcode arguments. Otherwise, you'd be limited
> > to a total of 256 of both.
>
> They're logically distinct things accessed by different opcodes for
> very different purposes. While you theoretically *could* use one array
> to hold both, it would make the eval code harder to read, and various
> introspection tasks (like "tell me all the names referenced from this
> code object") significantly more difficult.
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/agriff%40tin.it
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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 to check for the
traces.txt file. There are a number of them, but none contain
information about the segfault.

On Wed, Jan 28, 2015 at 11:23 AM, Ryan Gonzalez  wrote:
> 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 on, but it doesn't look as if it has started to
>> load modules yet.
>>
>> Does /dev/__properties__ ring a bell? Not to me.
>>
>
> https://android.googlesource.com/platform/system/core/+/tools_r22/init/property_service.c
> is the code that works with that file.
>
> This explains it a bit (slides 24-29). Looks like something to do with
> interprocess communication. Likely has nothing to do with Python itself.
>
> Maybe this would be useful?
>
>>
>> That stack trace would be really helpful.
>>
>> On Wed, Jan 28, 2015 at 8:34 AM, Cyd Haselton  wrote:
>>>
>>> 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
>>> _localemodule.c
>>>
>>> On Wed, Jan 28, 2015 at 9:43 AM, Guido van Rossum 
>>> wrote:
>>> > 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, 2015 at 6:43 AM, Cyd Haselton 
>>> > wrote:
>>> >>
>>> >> 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 build is reached...and when it is run as well (i.e.
>>> >> ./python --help, ./python -E -S -m sysconfig, or similar)
>>> >>
>>> >> I took a strace of ./python, however I'm a bit lost when reviewing it.
>>> >> Any ideas as to what may be going on...i.e. why Python 2.7 works but
>>> >> 3.x throws a segfault?
>>> >>
>>> >> Thanks in advance,
>>> >> Cyd
>>> >> ___
>>> >> Python-Dev mailing list
>>> >> Python-Dev@python.org
>>> >> https://mail.python.org/mailman/listinfo/python-dev
>>> >> Unsubscribe:
>>> >> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > --Guido van Rossum (python.org/~guido)
>>
>>
>>
>>
>> --
>> --Guido van Rossum (python.org/~guido)
>>
>> ___
>> Python-Dev mailing list
>> Python-Dev@python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe:
>> https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com
>>
>
>
>
> --
> Ryan
> If anybody ever asks me why I prefer C++ to C, my answer will be simple:
> "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
> nul-terminated."
> Personal reality distortion fields are immune to contradictory evidence. -
> srean
> Check out my website: http://kirbyfan64.github.io/
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] also

[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 etcetera
> for propellers and motors and stuff.
> 
> just having this in a main language seems to make a shit ton of sense.

You should check out Frink:

http://futureboy.us/frinkdocs/


-- 
Steve
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

[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, Cyd Haselton wrote:
>>
>> Noted. Will proceed with the 3.x releass.
>>
>> I had been excited you were working on Android Python until I realized you
>> were working on 2.x. I started with Python 3, and have only dabbled in 2.x
>> for a couple projects that had unported dependency needs. One of them,
>> reportlab, was ported in the last year, and the other is my web server CGI
>> ports which is still constrained by a couple libraries, and although I think
>> they may have recently been ported, I haven't had time to upgrade it.
>> Probably will by April, when I have to ditch my Google OpenID login system,
>> because they have abandoned it.
> Well, you can start being cautiously excited again now that I'm
> working on the 3.4.2 release.
>
> I use cautiously for several reasons...chief among them being the
> severely limited Android libc.
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/chris.barker%40noaa.gov
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com