- 134
- 2 694 852
PyCon 2015
Registrace 9. 04. 2015
Video
Keynote - Gabriella Coleman - PyCon 2015
zhlédnutí 7KPřed 9 lety
Keynote - Gabriella Coleman - PyCon 2015
Type Hints - Guido van Rossum - PyCon 2015
zhlédnutí 48KPřed 9 lety
Type Hints - Guido van Rossum - PyCon 2015
Jim Baker - Getting to Jython 2.7 and beyond - PyCon 2015
zhlédnutí 11KPřed 9 lety
"Speaker: Jim Baker So how did we get to Jython 2.7 anyway? And what are our future plans? In this talk, you will get a taste of how Jython works, some new functionality, and especially how Jython leverages both Python and Java to provide a very compatible solution. Slides can be found at: speakerdeck.com/pycon2015 and github.com/PyCon/2015-slides"
Mike Howsden - Zen of Quality - How PBS measures QoS for digital viewers - PyCon 2015
zhlédnutí 2,2KPřed 9 lety
"Speaker: Mike Howsden It is extremely important to PBS that digital viewers have an awesome experience when viewing online videos. In this talk, we explain how PBS built a system to collect, analyze, and measure who's getting a good experience and who's not. Slides can be found at: speakerdeck.com/pycon2015 and github.com/PyCon/2015-slides"
Luke Sneeringer - Improve your development environments with virtualization - PyCon 2015
zhlédnutí 8KPřed 9 lety
"Speaker: Luke Sneeringer A talk on how to employ virtualization to make development easier, more portable, and have it more closely adhere to production environments. Slides can be found at: speakerdeck.com/pycon2015 and github.com/PyCon/2015-slides"
Thomas Ballinger - Terminal whispering - PyCon 2015
zhlédnutí 19KPřed 9 lety
"Speaker: Thomas Ballinger Have you ever wanted to add a status bar to your command line program? Or maybe color the output a bit? Or do you want to write a fullscreen terminal application like ls, top, vim, or emacs? Then you need to speak a bit of terminal! This talk describes how to talk to your terminal from scratch and goes on to show why Python libraries Blessings and Urwid are so awesome...
Geoff Gerrietts - Performance by the Numbers: analyzing the performance of web applications
zhlédnutí 3,6KPřed 9 lety
"Speaker: Geoff Gerrietts Everyone knows poor performance when they see it, and performance concerns affect every application web applications more than most. But finding performance problems can be extraordinarily difficult, and requires an analytical approach coupled with good instrumentation. This talk explores approaches to instrumentation and what that instrumentation can tell you. Slides ...
Curtis Lassam - Hash Functions and You: Partners in Freedom - PyCon 2015
zhlédnutí 10KPřed 9 lety
"Speaker: Curtis Lassam Our trusty friend, the hash function, is as crucial to programming as linked lists or recursion, but it doesn't always get the press that it deserves. We're going to talk about hash functions, some data structures involving hash functions, the stately bloom filter, and the security implications of password hashing. Slides can be found at: speakerdeck.com/pycon2015 and gi...
Mica Swyers, Jay Chan - Finding Spammers & Scammers through Rate Tracking with Python & Redis
zhlédnutí 2,3KPřed 9 lety
"Speakers: Mica Swyers, Jay Chan This talk provides an introduction to rate tracking as well as an explanation of a particularly cool way to implement it. You will learn what rate tracking is, why you would want to do it, and then how you can use build a Redis-backed “velocity engine” in Python to do just that. Slides can be found at: speakerdeck.com/pycon2015 and github.com/PyCon/2015-slides"
Christine Spang - WebSockets from the Wire Up - PyCon 2015
zhlédnutí 6KPřed 9 lety
"Speaker: Christine Spang HTML5 WebSockets power the real-time web. Come take a deep dive into how they work, from the big picture down to what goes over the wire, including insight into the performance benefits of the protocol, via a real-world example of how WebSockets are implemented client- and server-side in Python. Slides can be found at: speakerdeck.com/pycon2015 and github.com/PyCon/201...
Tom Eastman - Serialization formats are not toys - PyCon 2015
zhlédnutí 9KPřed 9 lety
"Speaker: Tom Eastman It’s not in the OWASP Top 10, but you don’t have to look far to hear stories of security vulnerabilities involving deserialization of user input. In this talk I’ll go over what the threat is and how you might be making yourself vulnerable. I’ll cover the features (not bugs: features) of XML, YAML, and JSON that make them surprisingly dangerous, and how to protect your code...
---Incomplete talk --- A. Jesse Jiryu Davis - Python Performance Profiling: The Guts And The Glory
zhlédnutí 3,5KPřed 9 lety
Partial tutorial, due to a technical error only the beginning of the speak was recorded, sorry for the inconvenience "Speaker: A. Jesse Jiryu Davis Your Python program is too slow, and you need to optimize it. Where do you start? With the right tools, you can optimize your code where it counts. We’ll explore the guts of the Python profiler “Yappi” to understand its features and limitations. We’...
Pete Fein - Free Software, Free People - PyCon 2015
zhlédnutí 1,6KPřed 9 lety
"Speaker: Pete Fein Four years after the Arab Spring & 2 years after Snowden, little has changed. What now? This talk will remember Telecomix, an ad-hoc activist cluster that supported free communication around the world. Stories of humans and machines, reflection on 3 years of hacktivism & exploration of similarities to the free software community. It follows a 2011 Pycon lightning talk given ...
Sarah Bird - Interactive data for the web - Bokeh for web developers - PyCon 2015
zhlédnutí 26KPřed 9 lety
Sarah Bird - Interactive data for the web - Bokeh for web developers - PyCon 2015
Andrew Montalenti - streamparse: real-time streams with Python and Apache Storm - PyCon 2015
zhlédnutí 9KPřed 9 lety
Andrew Montalenti - streamparse: real-time streams with Python and Apache Storm - PyCon 2015
Ying Li - Where in your RAM is "python san_diego.py"? - PyCon 2015
zhlédnutí 4,1KPřed 9 lety
Ying Li - Where in your RAM is "python san_diego.py"? - PyCon 2015
Hynek Schlawack - Beyond grep: Practical Logging and Metrics - PyCon 2015
zhlédnutí 7KPřed 9 lety
Hynek Schlawack - Beyond grep: Practical Logging and Metrics - PyCon 2015
Smart services & smart clients: How micro-services change the way you build and deploy code.
zhlédnutí 4,4KPřed 9 lety
Smart services & smart clients: How micro-services change the way you build and deploy code.
Christine Spang - To ORM or not to ORM - PyCon 2015
zhlédnutí 4,2KPřed 9 lety
Christine Spang - To ORM or not to ORM - PyCon 2015
Keynote - Jacob Kaplan-Moss - Pycon 2015
zhlédnutí 77KPřed 9 lety
Keynote - Jacob Kaplan-Moss - Pycon 2015
Lightning Talks - April 11th 17h30 - Pycon 2015
zhlédnutí 5KPřed 9 lety
Lightning Talks - April 11th 17h30 - Pycon 2015
Lightning Talks - April 12th 08h30 - Pycon 2015
zhlédnutí 1,6KPřed 9 lety
Lightning Talks - April 12th 08h30 - Pycon 2015
Kathleen Danielson - Avoiding Burnout, and other essentials of Open Source Self-Care - PyCon 2015
zhlédnutí 2,9KPřed 9 lety
Kathleen Danielson - Avoiding Burnout, and other essentials of Open Source Self-Care - PyCon 2015
Jim Baker - A Winning Strategy with The Weakest Link: how to use weak references… - PyCon 2015
zhlédnutí 2,6KPřed 9 lety
Jim Baker - A Winning Strategy with The Weakest Link: how to use weak references… - PyCon 2015
Colton Myers - Managing Your Infrastructure with SaltStack - PyCon 2015
zhlédnutí 8KPřed 9 lety
Colton Myers - Managing Your Infrastructure with SaltStack - PyCon 2015
Nicholas Tollervey - Lessons learned with asyncio ("Look ma, I wrote a distributed hash table!")
zhlédnutí 4,3KPřed 9 lety
Nicholas Tollervey - Lessons learned with asyncio ("Look ma, I wrote a distributed hash table!")
Clayton Parker - So you think you can PDB? - PyCon 2015
zhlédnutí 14KPřed 9 lety
Clayton Parker - So you think you can PDB? - PyCon 2015
this is so cool. informative and an absolute breeze to follow. tysm
watching this after 10years... still relevant knowledge!!!
How can I build brain using python course.give me advice.I have to this courses with python.
I cannot imagine how much brain matter must be lost before one calls super() "well-designed".
Already in the first 5 minutes we have a glaring error. Multiple inheritance in python _never_ works, because there's no such thing as "classes without overlapping methods", because __init__ always overlaps, which means it's impossible to call __init__ correctly, which means it's flatly impossible to use multiple inheritance correctly in python. The author of super considered harmful understood this. You don't. Drop the smug and try to learn something.
Second glaring error, C3 linearization is not a "best and optimum solution to this problem", because it's not a solution to this problem in any sense. Turning multiple inheritance into single inheritance means there's no multiple inheritance at all, so you didn't solve the problem, so the thing doesn't. fricking. work. Funnily enough, multiple inheritance in C++ works just fine. You can use it. It works. You don't have to make all the classes aware of one another and demolish encapsulation to make it work. The author of super considered harmful understood this. You don't. Drop the smug and try to learn something.
More glaring errors I didn't bother to mention, but Pizza inheriting from DoughFactory? Come on.
No, it's not awesome that you can change the parent from the child, actually. It's insane, brittle, and impossible to use correctly. "is this fragile? no, it's deterministic" so is everything in programming. It's _extremely_ brittle. That's all the incompetence I can stomach, I'm afraid.
How did he figure this all out!?
27:56 LOL
Why PySide6 doesn't adhere to PEP 8 rules
Someone understands why he says ""the load is essentially offloaded somewhere else, you're not fighting with the GIL or anything like that..." 15:48 ? czcams.com/video/MCs5OvhV9S4/video.html The GIL is still limiting the task that are sent to the pool of threads right? Where are those task submitted otherwise ?
9 years in and still golden.
Don't know why this was promoted to me just now but I don't like that this video says it's 9 years old and from PyCon 2015. It adds up, but seems like it shouldn't.
The hilarious part of all of it is that unless your code won't change, none of these niceties will be maintainable within half of year.
Watching this in 2024, amazing talk 🫡👏👏
camelCaseIsSuperior
I guess I never thought anyone would have to remember imports since I do them all with pycharm
19:28 he recommends to create a new list every time but isn't that counter-intuitive? creating a new list means consuming more memory space while we can easily mutate the list. to me the first function is more efficient.
You can't exclude that specific line from pep8?
This talk: Looks like it's from 1995. It's actually from 2015. Is still useful in 2025.
This has to be one of the best videos introductions to Pandas out there, the simple structure of a dataset of movies provided the well thought exercises to test knowledge and to easily see the power of the library. My applause to Brandon I unlocked a new awesome tool to use.
I'm going to do a silly comment please don't take it seriously but I did a most casted actor as 'Himself' and the top result came to be 'Adolf Hitler', where is his IMDb page?
Thank you
"Do not learn to code from Google" - but why??
AUTOMATE THE BORING STUFF
Hi from 2023😊
what an awesome talk!
found thew talk to be useful even in 2023
I was looking for this exact explanation. Enjoyed the talk throughout.
Would it be bad practice (or helpful?) to write fib() as C module which releases the GIL? How much would that add overhead?
goodbye GIL <3
This speech is actual even for today! The best explanation of async programming it Python I've ever seen
No offense, but C++ saw this coming from before.
1:37:46 my respect for the man elevated immensely... 1:49:14 even more respect....
Wow this is amazing, and this logic can be applied to all of society and human nature. People will do as they're told, on average, but this psychology isn't a 1 or a 0 -- on or off --, it's a spectrum, and the tendency to start "fixing" problems while ignoring the underlying issues is a big part of that. When the "bosses" or creators of the code bases and big industry want more integration between code bases and code that's easier to read and update, intuitively it's a good idea to focus on prettying it up, but coders are engineers, and engineers should always always always be focused on making the simplest version of the task at hand. Look at any old invention that still works today and you'll see things people would scoff at were it not 100% fact that it works flawlessly. That's old code. The engineers and creators of today may follow more standards, and may be more organized, but we're all human, and the gorilla in the room is all the things beyond the famous quote: "Perfection is Achieved Not When There Is Nothing More to Add, But When There Is Nothing Left to Take Away" -Antoine de Saint-Exupery
PEP8 unto thyself, not unto others😂 (Well unless you MUST leave a comment in a code review)
Few questions about DI in this style. 1. How do you handle injecting a class that itself needs dependencies injected? Does the entire app become one class eventually? 2. How do you track down everything that can be injected and what method signatures are expected for each? 3. What happens if an interface is implemented wrongly and has a wrong return type? 4. What happens if two different dependencies that are both required happen to have the same method names? 5. Looks like you choose concrete implementations at the time of class declaration instead of within a configuration file (which governs class instantiation later on) like the DI libraries that I'm used to. What if I don't know some of the concrete dependencies at the time of class declaration of the base class and I only know that it will follow a certain interface? DI is usually a tool for class composition. In other words it deals with "has-a" relationships rather than "is-a" relationships. So it's really strange to see a language feature that facilitates class-based inheritance being suggested as a tool for DI. The result seems to be similar to a mixin pattern for sharing functionality (with all its criticisms) with extra attention to the MRO navigate the confusing nature of this language feature.
1. The same, just inject previously into the class you need. No, the entire app does not become 1 class. 2. Not sure what you mean by 'track down'? Don't overcomplicate things, ptyhon design is different. Don't bring here fancy terms like 'method signatures', they don't make sense in this context. 3. Change your code. 4. Good point. The method resolution order will resolve to the first one encountered if you use super with no arguments. Super can be used with arguments that direct its resolution. So, without arguments, it resolves with the c3 algorithm. With arguments you can call 1 or both in the order you need ( In that specific case you do introduce a little redundancy, but you have no choice). 5. Again, python is more abstract. An interface is just a contract or a declaration of behavior. You could just class Interface: def act(self): pass class Imp(Interface): pass You could use the ABC (Abstract Base Class) module to decorate and express and force the interpreter to put some restrictions, like, not implementing Interface.act method. Don't let them confuse you with fancy words 'implements' 'extends' and 'injection', behind the scenes there are just objects and pointers. In Python, I don't care if put my dependency inside the parenthesis of a class declaration if I'm given the dependency at the instance creation level or if I fucking give a framework a yaml file that declares my dependencies and makes the symbols available at the necessary scope. It's a matter of understanding the best approach for you. Again, in this case, is trivial, discussing the 'is-a' or 'has-a' thing is a waste of time and is inherited by old paradigms. The difference is just this: class Dependant(Dependency): # what you call 'is-a' pass or class Dependant: # what you call 'has-a' def __init__(self, dependency): self.dependency = dependency or, if you want a framework: dependencies.yaml Dependant Dependency -- Then in your code: Dependant().dependency.method_on_dependency() Do you see how dumb it is to waste time discussing this? It's nice as a learning exercise but at the end of the day, why the hell i would go and create a file and install a framework if I can just write class A(B): pass? What is the advantage of expressing this particular case in a file instead of in the code file itself? If you find dependencies later, just go and add a new dependency to your class Instantiation (Yes, classes in Python are first-class citizens). You are too biased. If your dependency is against an interface, and you know it, then add the interface. If you don't know it, it is not a problem with the language. That's it. When you call the method it will just do nothing, or again, you can decorate to enforce classic oo behavior like raising a NotImplemented error and stuff like that, or even raise a not implemented error. Python is very abstract and that is why it gives you so much flexibility. These ideas become clear to you when you become older. You need to work in too many different areas and technologies to understand all is reduced to a matter of convenience and automation. Some principles should guide you, but these are not dependent on the technologies. Behind the scenes, all is reduced to objects and pointers. How do you think a class Inheritance is resolved inside the compiler? So, for example, they say "Favor composition over inheritance". Ok. That may be good for Java | C# | C++ but, what if I have a language that has a method resolution and leaves me to declare my dependencies at class Instantiation level, I mean here: class A(B, C). Then what is the difference between receiving the dependency from a config file, or 'injected' at the instance instantiation level? I can test and refactor at any time. Convenience, Man. Hope you undersand.
Came here from "Beyond the basic stuff with python" :)
Love it!!! Miguel's own style of teaching is great. That reminds me the other great teachers are David J. Malan, Brian Yu and many others at the CS50.
Corey Schafer is also great.
AHA! For the old asm/C programmers out there, the money shot is 20:15. Names/variables have scope, whereas all (allocated) values are on the heap and only 'leave scope' when the last reference to them leaves scope.
Raymond Hettinger is the best public speaker I think I've ever seen
This is called "intellectually"
I learn how to use fake over mocking via Robot's example. Amazing!
These 3-hour D. Beazley talks are awesome.
Excellent tutorial even if this was back in 2015 😃
For the 2D list in the last slide, here is Amy's talk section covering that czcams.com/video/sH4XF6pKKmk/video.html
I've been programming in python for almost 10 years, and I still learned something new today!!!
College is such garbage
Excellent talk! Thank you! :)
epic explanation completely shock my understanding of variables and lists
I'm watching this like 7 years later and it still blows my mind how such a simple talk can have a profound impact on how you approach problems
I don't like Pepe.
I agree on all the points except one: I prefer to make EVERY code, with exclusion of the most application-specific maybe, a part of my own library, to never have to write it second time (DRY principle at work). I would also give more attention to careful designing of public entrypoints parameter types and names, using SOLID, but author thinks it's more extensibility than reusability.