We're just getting started, so please use this thread to suggest what this community should look like, what it should cover, and how it should operate.

all 18 comments

sorted by: hot top controversial new old

[–] jim 7 points 1 year ago (1 children)

The code in the community's banner is in python 2. Can we get that changed?

[–] jnovinger 2 points 1 year ago

Ha! Great catch. Yeah, I'll get that sorted.

[–] [email protected] 4 points 1 year ago

I don't know, I just got here.

Here being only just starting to learn python. And also this community too.

[–] erre 3 points 1 year ago

I'm subbing to, ideally, keep up to date with latest trends and best practices 🙂

[–] jnovinger 3 points 1 year ago

Next experiment is Talk Tuesday where each top-level comment is about a particular conference talk that a commenter liked and why they like it.

[–] [email protected] 3 points 1 year ago (1 children)

Hi Jason, Thanks for putting this community together! I've been passively teaching myself Python for awhile to add to my toolkit. I saw in your bio you're involved with sports data at Elias. That's super cool! I'd be curious to learn more about what tools and how Python is used in sports data analysis. Cheers 😀

[–] jnovinger 1 points 1 year ago

Thanks @[email protected] , I think I was just in the right place at the right time.

I'll see if I can dig up some old technical blog posts from work. On my current project, we're using Python for a research SaaS tool for sports information people, generally at broadcasters and league offices. We also have a fair amount of ETL type code in Python for aggregating and enriching data.

[–] jnovinger 2 points 1 year ago (1 children)

Also trying out Today in Python!. I accidentally launched the first one early, in that I posted about 20 June 2023 on 19 June 2023. Whoops.

[–] jnovinger 2 points 1 year ago

This proved to be a fair amount of work, absent a bot of some sort that I haven't had time to create yet.

So, I failed toward just including events in the sidebar, with a link to python.org's Event Calendar.

[–] jnovinger 2 points 1 year ago

Thought I would also keep track of things we experiment with here. The first is Media Mondays where we track podcast and video episode from the community over the last week.

[–] UlrikHD 1 points 5 months ago (1 children)

@[email protected]

Just a reminder that we sent you a DM some time ago, but have yet to receive an answer. Happy cake day :)

-The admin team

[–] jnovinger 1 points 5 months ago (1 children)

Hey Ulrik, apologies for not responding sooner.

I'm more than happy to talk about adding one (or more!) mods for any of the communities I mod for right now, including c/python. I have at least one person in mind, who has been pretty active both in c/python and c/django. I'd also like to talk more about mod expectations, particularly with regard to reported posts/comments.

[–] UlrikHD 1 points 5 months ago

From the perspective of the admin team, as long as reports are consistently resolved in a timely manner we are happy.

If you have any questions or want help with finding extra moderators, feel free to ask it here or via DM, otherwise we also have a Discord server and a Matrix space where we can talk.

[–] stOneskull 0 points 1 year ago* (last edited 1 year ago) (1 children)

i wonder what python version should be recommended as standard? should it be what debian stable currently has as its lastest? i've found some things can't handle the new-ness of 3.11. so is it 3.10?

[–] qwop 2 points 1 year ago (1 children)

3.11 has been out long enough that it is supported by almost all mainstream libraries now. Unless you have a reason to use an older version (of which there are quite a few to be fair), 3.11 would be my default.

[–] stOneskull 1 points 1 year ago* (last edited 1 year ago)

the OpenAI API doesn't like 3.11 at the moment but yeah, it's easy enough to use an earlier version, especially with conda