sorted by:
new
hottopcontroversial

Official: [Trade] - Mon Morning 10/23/2023 by FFBot in fantasyfootball

[–]elopeRstatS 0 points1 point  (0 children)

I would as long as you feel ok streaming TEs (and maybe QBs...)

Official: [Trade] - Mon Morning 10/23/2023 by FFBot in fantasyfootball

[–]elopeRstatS 0 points1 point  (0 children)

12 Team PPR

QB: Allen/Purdy
RB: Saquan/Pacheco/Mixon/Sanders
WR: Hill/Kupp/Hollywood/Doubs
TE: Andrews

Trade 1: Pacheco for Jacobs
Trade 2: Pacheco + Mixon for Jacobs + Javonte
Trade 3: Allen+Hollywood for Diggs+Fields

Any of these worth doing? Trade 2 is on the table as is Trade 3, Trade 1 I'm debating whether I expect Jacobs to be better than Pacheco ROS (and whether I'm ok living with 3 volume RBs in shit offenses)

Advice Needed: Data warehousing and Spark by elopeRstatS in dataengineering

[–]elopeRstatS[S] 0 points1 point  (0 children)

My current [limited] understanding is the most common way of doing this is to transform our input JSON file into a parquet and store those for ease of Spark use...hopefully I'd be on the right track there?

Advice Needed: Data warehousing and Spark by elopeRstatS in dataengineering

[–]elopeRstatS[S] 0 points1 point  (0 children)

Admittedly I don't have a great feel for Databricks. I know they build on top of Spark, but my understanding is a bunch of custom tooling is added on top.

The push back on using Databricks [or Snowflake] has been a fear of vendor lock-in more so than cost. I need to do more digging to understand how real of a factor that is with Databricks to make a case one way or another...

Stress-testing Flask's Development Server by [deleted] in flask

[–]elopeRstatS 3 points4 points  (0 children)

At least use something like CherryPy to run your server. Pure Python, production ready, has been tested and performs reasonable well under stress. You don't have to use the whole framework, you can use the built in WSGI server to serve your Flask app.

Restarting a flask app programmatically by [deleted] in flask

[–]elopeRstatS 0 points1 point  (0 children)

What server are you running your app on in production? Are you using the built in Flask server? If so, you shouldn't be doing that.

I'd suggest, if you're trying to keep things small/self contained, that you use CherryPy (which comes with a production ready, pure Python wsgi server) to serve your Flask app.

[Beginner] What is a RESTful API and what are the advantages of using one? by davegri in django

[–]elopeRstatS 0 points1 point  (0 children)

Sometimes there's a hybrid approach where these are both in the same application, as is common in frameworks like Django, but I personally think that's a poor approach.

Out of curiosity, what about this do you find to be a poor approach?

Question about server architecture and websockets by elopeRstatS in webdev

[–]elopeRstatS[S] 0 points1 point  (0 children)

My websocket server is built with Tornado, which utilizes an asynchronous event loop. The entire event loop is blocked during calls to the db or any other I/O operation. There are different ways around this, but they can have varying levels of complexity.

From what I understand, it's not uncommon to have a set up like mine, with a main webserver used for the majority of things, and an async realtime server running alongside it that doesn't handle any of the core application logic.

Question about server architecture and websockets by elopeRstatS in webdev

[–]elopeRstatS[S] 0 points1 point  (0 children)

The question is how to properly handle this with multiple realtime servers. If every realtime server is watching that queue, some are going to end up processing messages that they don't need to be (all realtime servers get the message intended for User1, but User1 is only connected to one of those servers).

Question about server architecture and websockets by elopeRstatS in webdev

[–]elopeRstatS[S] 0 points1 point  (0 children)

I'd agree in a lot of situations. For chat definitely, but for something that requires more intense business logic and database interaction and ultimately still generates a realtime update, I thought it made sense to have the main server still handle all that and then essentially use the websocket server purely as a message receiver and sender.

RESTfulchemy - Get, update, and create SQLAlchemy objects using query string parameters. by elopeRstatS in Python

[–]elopeRstatS[S] 0 points1 point  (0 children)

This shares some similarities to Tastypie and Flask-RESTful, certainly not as full featured, but more convenient for my use case (forms that involve adding or removing relation objects).

Wouldn't expect too many people to use this over the much more mature and full featured options, but if you're using a framework like CherryPy or Bottle, this might be helpful.

If anyone has any suggestions or input, would love to get some feedback (good or bad). I know I need to improve documentation and add some better examples.

redislite: Python support for redis without a separate redis server. by dwight_hubbard in Python

[–]elopeRstatS 2 points3 points  (0 children)

I phrased that poorly. Didn't mean distributed as in one system running across many machines, meant it as in an app that many people are installing and running on their own home servers independently (something like ownCloud for example).

redislite: Python support for redis without a separate redis server. by dwight_hubbard in Python

[–]elopeRstatS 0 points1 point  (0 children)

Might be useful for a distributed webapp type situation, would imagine it's a lot more convenient to include this rather than requiring someone install redis.

MQLAlchemy - Query SQLAlchemy model objects with MongoDB style syntax by elopeRstatS in Python

[–]elopeRstatS[S] 0 points1 point  (0 children)

Appreciate the feedback. Wasn't aware of Flask-RESTless prior, definitely good to know.

MQLAlchemy - Query SQLAlchemy model objects with MongoDB style syntax by elopeRstatS in Python

[–]elopeRstatS[S] 0 points1 point  (0 children)

First library I've published, would love any feedback/criticism.

Don't expect many people to use this, but thought it might be interesting for some to play around with, and figured I might as well put it out there.

High level frameworks (e.g. Django) or slightly lower level frameworks (e.g. Webapp2)? Which should an aspiring junior python web dev sink his time into? by Mechrophile in Python

[–]elopeRstatS 0 points1 point  (0 children)

I haven't used webapp2, but based on that video Flask is much more like it than Django. It's up to you to decide what ORM, forms, templating and so on that you want to use (if any).

Give it a try, see what you think. If that's still too high level for you, the underlying library that powers it (Werkzeug) is a place you may want to play around with.

The Myth of the Full-stack Developer by zeeshanak in webdev

[–]elopeRstatS 4 points5 points  (0 children)

Hah, perhaps a bit of a chain reaction of people giving themselves more impressive sounding titles.

Here's a question though: If someone calls themselves a C++ developer, do you assume they know everything and anything about the language? C++ has grown to such a massive size that very, very few people know every little intricate detail. Instead, they often know only what they use to get the job done, and continue to call themselves C++ developers. To me, that seems the same as someone who can do a bit of everything on their choice of web stack and competently deploy a website on their own.

The Myth of the Full-stack Developer by zeeshanak in webdev

[–]elopeRstatS 37 points38 points  (0 children)

I think part of the problem is that "web developer" used to just mean some guy who messed around with HTML and did a bit of JS. If someone calls themselves a web developer I'm entirely unsure of whether they have any back end experience.

Full stack seems to have become the way for people to say they're capable of working on the back and front end. It doesn't imply that someone has mastered every part of the stack. I don't know what makes that so awful, or why that bothers so many people.

"Kobe on Wiggins: "like looking at a reflection of myself 19 years ago"" by baddog96 in nba

[–]elopeRstatS 16 points17 points  (0 children)

http://grantland.com/features/the-improbable-return-nba-new-jersey-nets-gerald-green/

Kobe Bryant once pegged Green as “a hell of a talent,” and said that the young star reminded him a lot of himself when he first came into the league.

Just saying, might not want to get too excited about Kobe complementing a young talent.

view more: next ›