This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
Yes I agree, e.g. in Python I use pd.DatetimeIndex.tz_localize to help me with this (after spending my first two years as a quant doing things manually before throwing my hands up and realizing that this is a common problem everyone must be having, so someone somewhere has probably created a good solution).
However needing to import it and write like an extra 10 lines of code for every single project I wouldn't need to do if DST (shakes fist) didn't exist adds up over time to become a serious pain in the ass. Plus now my script has an extra dependency and is more susceptible to code bitrot over time as it'll stop working if pd.DatetimeIndex gets its behaviour changed or deprecated.
Also SQL doesn't play nicely with timezones at all, so the problem still very much exists for SQL scripts unless you only want to use SQL to pull the data and will do all your analysis with the pulled data in a different language.
Well, that's your mistake - I'm talking about the standard library, not pandas. No dependency, no bitrot. No need to localize any
datetimes until you're displaying them, so as long as you aren't working with naive datetimes it's pretty low overhead.As SQL is fundamentally not a serious language, it indeed does not support
zoneinfo.More options
Context Copy link
More options
Context Copy link