home.social

#biopython — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #biopython, aggregated by home.social.

  1. @dalke thank you Andrew for your thoughtful reply (and past contributions to #Biopython and #BOSC which is also still going strong): mailman.open-bio.org/pipermail

  2. I've started an email thread "Generative AI policy for contributions to Biopython" which I hope will lead to a pull request laying out some guidelines for acceptance of AI assisted contributions (personally I'd like to just reject them, but doubt that stance is universally held with the current pool of maintainers, we'll see): mailman.open-bio.org/pipermail #Biopython

  3. Seems the recent #GenerativeAI #slop pull requests that I've looked at for #Biopython have preferentially targeted the "Good First Issues". We really wanted those to be onboarding ramps for new #OpenSource contributors - and not for padding anyone's GitHub profile or whatever the motivation here is.

    So I think any formal policy will want to say explicitly #NoAI on those issues at the very least.

  4. The #GenerativeAI #slop pull requests to #Biopython seem to be on the rise - github.com/biopython/biopython might help?

    Failing to use the PR template is definitely a red flag 🚩

  5. How I Built a Machine Learning Tool to Predict Drug Manufacturing Failures

    A bioprocess engineer's journey into machine learning and why the pharmaceutical industry desperately needs this bridge When I tell people I work in bioprocess engineering, I usually get blank stares. When I explain that I help manufacture proteins in giant tanks for therapeutic use, the response is often: "Oh, like brewing beer?" Not quite. But close enough. What I don't usually mention is that I've been teaching myself machine learning on nights and weekends. Not because it's trendy, but […]

    kemal.yaylali.uk/from-bioreact

  6. From Bioreactors to AI: How I Built a Machine Learning Tool to Predict Drug Manufacturing Failures

    *A bioprocess engineer's journey into machine learning—and why the pharmaceutical industry desperately needs this bridge* --- When I tell people I work in bioprocess engineering, I usually get blank stares. When I explain that I help manufacture proteins in giant tanks for therapeutic use, the response is often: "Oh, like brewing beer?" Not quite. But close enough. The $50 Million Problem Nobody Talks About What I don't usually mention is that I've been teaching myself machine learning […]

    kemal.yaylali.uk/from-bioreact

  7. From Bioreactors to AI: How I Built a Machine Learning Tool to Predict Drug Manufacturing Failures

    *A bioprocess engineer's journey into machine learning—and why the pharmaceutical industry desperately needs this bridge* --- When I tell people I work in bioprocess engineering, I usually get blank stares. When I explain that I help manufacture proteins in giant tanks for therapeutic use, the response is often: "Oh, like brewing beer?" Not quite. But close enough. The $50 Million Problem Nobody Talks About What I don't usually mention is that I've been teaching myself machine learning […]

    kemal.yaylali.uk/from-bioreact

  8. @sethmlarson we use the library-specific not-silent-by-default warning in #Biopython and it still catches people out when stuff is removed 🤷 github.com/biopython/biopython

  9. I blogged my thoughts on receiving generative AI contributions as an Open Source project maintainer blastedbio.blogspot.com/2025/1 - seen with #Bioinformatics and #Biopython in particular in mind, but most of these issues are generic to #OpenSource development. It worries me #GenAI

  10. I got approached today at #ISMBECCB2025 #BOSC2025 with “Are you the pyANI guy?” (Re github.com/pyani-plus/pyani-pl - and yes, one of them).

    Confusing as I’m more used to being called the “#Biopython guy” 🤣

  11. I got approached today at #ISMBECCB2025 #BOSC2025 with “Are you the pyANI guy?” (Re github.com/pyani-plus/pyani-pl - and yes, one of them).

    Confusing as I’m more used to being called the “#Biopython guy” 🤣

  12. I got approached today at #ISMBECCB2025 #BOSC2025 with “Are you the pyANI guy?” (Re github.com/pyani-plus/pyani-pl - and yes, one of them).

    Confusing as I’m more used to being called the “#Biopython guy” 🤣

  13. I got approached today at #ISMBECCB2025 #BOSC2025 with “Are you the pyANI guy?” (Re github.com/pyani-plus/pyani-pl - and yes, one of them).

    Confusing as I’m more used to being called the “#Biopython guy” 🤣

  14. I got approached today at #ISMBECCB2025 #BOSC2025 with “Are you the pyANI guy?” (Re github.com/pyani-plus/pyani-pl - and yes, one of them).

    Confusing as I’m more used to being called the “#Biopython guy” 🤣

  15. The first #biopython mention I’ve caught at #ISMBECCB2025, in the context of pyJASPAR for accessing JASPAR motifs in Python - “JASPAR-Suite: An open toolkit for accessing TF binding motifs” by Aziz Khan #BOSC2025 🧬🐍👍

  16. @OpenBio only noticed the typo now: it is available on PyPI, but I meant we test running #Biopython under the #PyPy implementation of Python

  17. @OpenBio The next commit/pull request will put the #Biopython git repository’s default branch at over 16,000 commits!

  18. Big city life - triaging #Biopython bug reports while finishing my latte in a trendy cafe in Glasgow.

  19. @gedankenstuecke @gravitystorm @openstreetmap The OSM number of contributors looks several magnitudes higher than for #biopython (not surprising), but we’ve not finished our relicensing effort yet 😅

  20. @Edent Python has a tradition of functional testing of doctests in docstrings (code snippets within the API docs), and I use a generalised version of this for our main docs in #Biopython.

    However that doesn’t solve this use case of testing installation instructions - which seems doable in principle but complex to orchestrate. I wonder if there’s something off the shelf which covers the basics (in Python in particular)? …

  21. @pjacock #BioPython has 114 open pull requests? That seems excessive.

  22. Also, does #Biopython need to be on Mastodon (we have/had an account on Twitter)?

  23. We’ll be working on releasing #Biopython 1.82 fairly soon mailman.open-bio.org/pipermail - if you’ve got a favourite issue or pull request which you think should go in, please speak up now.

  24. Way overdue, but #Biopython 1.80 is out pypi.org/project/biopython/1.8 - expect formal announcement later mailman.open-bio.org/pipermail - conda packages soon too! Thank you to all the contributors