News for hackers. Stuff that matters.
Re:Python 3.5.0 by inglor on Sunday September 13, 2015 @03:42PM (#10212548)
It has the ability to statically check the type system, that's amazing. Moreover async/await with async resource management (which C# doesn't have yet) gives it a real edge for server development.
Re:Python 3.5.0 by sadgit on Sunday September 13, 2015 @07:41PM (#10213140)
> has the ability to statically check the type system

I was under the impression that type checking was not one of the goals of PEP 484 etc.

Re:Python 3.5.0 by useerup on Monday September 14, 2015 @12:48AM (#10213677)
> Moreover async/await with async resource management (which C# doesn't have yet)

In C#, the using statement combines with async/await. It is cool that Python finally gains proper async/await, there is no need to diss other languages.

Re:Python 3.5.0 by inglor on Monday September 14, 2015 @10:14AM (#10215135)
IDisposable's dispose is not an async function, there is no IAsyncDisposable interface with language support. There is however, a proposal https://github.com/dotnet/roslyn/issues/114 , I'm not dissing the language but things are the way they are.
Re:Python 3.5.0 by ColinDabritz on Sunday September 13, 2015 @03:52PM (#10212584)
What is async resource management? can you link to docs for the features you mean? I'm having trouble googling this one, maybe different keywords are used?
Re:Python 3.5.0 by 1st1 on Sunday September 13, 2015 @04:18PM (#10212679)
I think inglor refers to the new 'async with' statement: https://docs.python.org/3/reference/compound_stmts.html#asyn...

Using it you can safely cleanup/commit transaction/release lock/etc when exiting a block of statements (even if an exception was raised). Plain 'with' statement cannot call asynchronous code in '__exit__' methods, 'async with' can do that (in '__aexit__').

Re:Python 3.5.0 by jodah on Monday September 14, 2015 @01:29PM (#10216225)
> async/await with async resource management (which C# doesn't have yet) gives it a real edge for server development

An edge over what? You're still limited to a single thread via the GIL. Until that problem is solved, Python is certainly not the best bet (all else aside) for server development.

Re:Python 3.5.0 by cben on Saturday September 19, 2015 @05:31PM (#10245599)
Node.js is also single thread and has been doing fine on servers.

Do you really need to share mutable state between threads in your server? If yes, what's your story when you'll need to scale to multiple servers?

If not because you can keep shared mutable state in a separate service (DB or similar), you can deal with one-machine scaling very similarly to scaling across machines - just start/fork a process per CPU. You get simplicity, avoid the whole thread-safety can of bugs, and all the administration benefits of stateless servers.