home.social

#pythonpackage — Public Fediverse posts

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

  1. Have any big Python packages moved off of Github given the general wtfery going on there?

    I’m considering moving my package elsewhere and I think the only thing I would miss would be the nice CI workflow for publishing to PyPI, unless that is also portable?

    #python #pypi #pythonpackage

  2. Have any big Python packages moved off of Github given the general wtfery going on there?

    I’m considering moving my package elsewhere and I think the only thing I would miss would be the nice CI workflow for publishing to PyPI, unless that is also portable?

    #python #pypi #pythonpackage

  3. Have any big Python packages moved off of Github given the general wtfery going on there?

    I’m considering moving my package elsewhere and I think the only thing I would miss would be the nice CI workflow for publishing to PyPI, unless that is also portable?

    #python #pypi #pythonpackage

  4. Have any big Python packages moved off of Github given the general wtfery going on there?

    I’m considering moving my package elsewhere and I think the only thing I would miss would be the nice CI workflow for publishing to PyPI, unless that is also portable?

    #python #pypi #pythonpackage

  5. Have any big Python packages moved off of Github given the general wtfery going on there?

    I’m considering moving my package elsewhere and I think the only thing I would miss would be the nice CI workflow for publishing to PyPI, unless that is also portable?

    #python #pypi #pythonpackage

  6. Hi lazyweb, a #Python package question. The structure:

    packagerepo
    ↳ mystuff
    ↳ __init__.py
    ↳ mystuff.py
    ↳ extraA.py

    I want mystuff.py to be "the package" such that anyone using it can write

    from mystuff import ...

    to get identifiers from mystuff.py. With __init__.py being

    from .mystuff import *

    this looks OK.

    Yet pydoctor does not show this correctly. May be a pydoctor thing, but maybe there is a better way than this import in __init__.py ?

    #pythonpackage

  7. Hi lazyweb, a #Python package question. The structure:

    packagerepo
    ↳ mystuff
    ↳ __init__.py
    ↳ mystuff.py
    ↳ extraA.py

    I want mystuff.py to be "the package" such that anyone using it can write

    from mystuff import ...

    to get identifiers from mystuff.py. With __init__.py being

    from .mystuff import *

    this looks OK.

    Yet pydoctor does not show this correctly. May be a pydoctor thing, but maybe there is a better way than this import in __init__.py ?

    #pythonpackage

  8. Hi lazyweb, a #Python package question. The structure:

    packagerepo
    ↳ mystuff
    ↳ __init__.py
    ↳ mystuff.py
    ↳ extraA.py

    I want mystuff.py to be "the package" such that anyone using it can write

    from mystuff import ...

    to get identifiers from mystuff.py. With __init__.py being

    from .mystuff import *

    this looks OK.

    Yet pydoctor does not show this correctly. May be a pydoctor thing, but maybe there is a better way than this import in __init__.py ?

    #pythonpackage

  9. Hi lazyweb, a #Python package question. The structure:

    packagerepo
    ↳ mystuff
    ↳ __init__.py
    ↳ mystuff.py
    ↳ extraA.py

    I want mystuff.py to be "the package" such that anyone using it can write

    from mystuff import ...

    to get identifiers from mystuff.py. With __init__.py being

    from .mystuff import *

    this looks OK.

    Yet pydoctor does not show this correctly. May be a pydoctor thing, but maybe there is a better way than this import in __init__.py ?

    #pythonpackage

  10. Hi lazyweb, a #Python package question. The structure:

    packagerepo
    ↳ mystuff
    ↳ __init__.py
    ↳ mystuff.py
    ↳ extraA.py

    I want mystuff.py to be "the package" such that anyone using it can write

    from mystuff import ...

    to get identifiers from mystuff.py. With __init__.py being

    from .mystuff import *

    this looks OK.

    Yet pydoctor does not show this correctly. May be a pydoctor thing, but maybe there is a better way than this import in __init__.py ?

    #pythonpackage

  11. Was steckt hinter einem NFDInspector?

    Findet es heraus im Workshop unseres Incubator Funds Projektes von Montanhistorischen Dokumentationszentrums des Deutschen Bergbaumuseums Bochum!

    Weitere Infos zum Workshop und der Entwicklung des Python Packages: 4memory.de/2024/08/30/nfdiinsp

    Zur Anmeldung für das Community Forum: conftool.org/digital-humanitie

    #NFDI4Memory #montandok #NFDI #DeutschesBergbauMuseum #Python #PythonPackage #Qualitätsprüfung #Museen #Archive

  12. Was steckt hinter einem NFDInspector?

    Findet es heraus im Workshop unseres Incubator Funds Projektes von Montanhistorischen Dokumentationszentrums des Deutschen Bergbaumuseums Bochum!

    Weitere Infos zum Workshop und der Entwicklung des Python Packages: 4memory.de/2024/08/30/nfdiinsp

    Zur Anmeldung für das Community Forum: conftool.org/digital-humanitie

    #NFDI4Memory #montandok #NFDI #DeutschesBergbauMuseum #Python #PythonPackage #Qualitätsprüfung #Museen #Archive

  13. Was steckt hinter einem NFDInspector?

    Findet es heraus im Workshop unseres Incubator Funds Projektes von Montanhistorischen Dokumentationszentrums des Deutschen Bergbaumuseums Bochum!

    Weitere Infos zum Workshop und der Entwicklung des Python Packages: 4memory.de/2024/08/30/nfdiinsp

    Zur Anmeldung für das Community Forum: conftool.org/digital-humanitie

    #NFDI4Memory #montandok #NFDI #DeutschesBergbauMuseum #Python #PythonPackage #Qualitätsprüfung #Museen #Archive

  14. Was steckt hinter einem NFDInspector?

    Findet es heraus im Workshop unseres Incubator Funds Projektes von Montanhistorischen Dokumentationszentrums des Deutschen Bergbaumuseums Bochum!

    Weitere Infos zum Workshop und der Entwicklung des Python Packages: 4memory.de/2024/08/30/nfdiinsp

    Zur Anmeldung für das Community Forum: conftool.org/digital-humanitie

    #NFDI4Memory #montandok #NFDI #DeutschesBergbauMuseum #Python #PythonPackage #Qualitätsprüfung #Museen #Archive

  15. Was steckt hinter einem NFDInspector?

    Findet es heraus im Workshop unseres Incubator Funds Projektes von Montanhistorischen Dokumentationszentrums des Deutschen Bergbaumuseums Bochum!

    Weitere Infos zum Workshop und der Entwicklung des Python Packages: 4memory.de/2024/08/30/nfdiinsp

    Zur Anmeldung für das Community Forum: conftool.org/digital-humanitie

    #NFDI4Memory #montandok #NFDI #DeutschesBergbauMuseum #Python #PythonPackage #Qualitätsprüfung #Museen #Archive

  16. pip install xgi

    And get started streamlining your processes for working with higher-order networks from start to finish! XGI is part of the ecosystem, and excels at many things, including:

    🔍 Analyzing higher-order networks with measures and algorithms
    🧰 Manipulating node and edge statistics in a flexible and customizable way
    🎨 Drawing higher-order networks in a variety of visually striking ways

    📄 XGI docs: xgi.readthedocs.io/en/stable/

  17. pip install xgi

    And get started streamlining your processes for working with higher-order networks from start to finish! XGI is part of the #pyOpenSci ecosystem, and excels at many things, including:

    🔍 Analyzing higher-order networks with measures and algorithms
    🧰 Manipulating node and edge statistics in a flexible and customizable way
    🎨 Drawing higher-order networks in a variety of visually striking ways

    📄 XGI docs: xgi.readthedocs.io/en/stable/

    #opensource #openscience #python #pythonpackage

  18. pip install xgi

    And get started streamlining your processes for working with higher-order networks from start to finish! XGI is part of the #pyOpenSci ecosystem, and excels at many things, including:

    🔍 Analyzing higher-order networks with measures and algorithms
    🧰 Manipulating node and edge statistics in a flexible and customizable way
    🎨 Drawing higher-order networks in a variety of visually striking ways

    📄 XGI docs: xgi.readthedocs.io/en/stable/

    #opensource #openscience #python #pythonpackage

  19. pip install xgi

    And get started streamlining your processes for working with higher-order networks from start to finish! XGI is part of the #pyOpenSci ecosystem, and excels at many things, including:

    🔍 Analyzing higher-order networks with measures and algorithms
    🧰 Manipulating node and edge statistics in a flexible and customizable way
    🎨 Drawing higher-order networks in a variety of visually striking ways

    📄 XGI docs: xgi.readthedocs.io/en/stable/

    #opensource #openscience #python #pythonpackage

  20. pip install xgi

    And get started streamlining your processes for working with higher-order networks from start to finish! XGI is part of the #pyOpenSci ecosystem, and excels at many things, including:

    🔍 Analyzing higher-order networks with measures and algorithms
    🧰 Manipulating node and edge statistics in a flexible and customizable way
    🎨 Drawing higher-order networks in a variety of visually striking ways

    📄 XGI docs: xgi.readthedocs.io/en/stable/

    #opensource #openscience #python #pythonpackage

  21. Sehen wir uns morgen in der Lunch Break @ 4Memory Incubator Funds?

    Von 12:30 bis 13:30 Uhr stellen das Deutsche Bergbau-Museum Bochum & Koordinationsstelle für Provenienzforschung in NRW die nächsten beiden 4Memory Incubator Funds Projekte vor, seid gespannt!

    Teilnehmen ist ganz einfach, ohne Voranmeldung über BBB: bbb.rlp.net/rooms/ttu-ktp-njp-

    #NFDI #NFDIrocks #NFDI4Memory #IncubatorFunds #LunchBreak #FDM #provenienzforschung #Bergbaumuseum #MaschinellesSehen #PythonPackage

  22. Sehen wir uns morgen in der Lunch Break @ 4Memory Incubator Funds?

    Von 12:30 bis 13:30 Uhr stellen das Deutsche Bergbau-Museum Bochum & Koordinationsstelle für Provenienzforschung in NRW die nächsten beiden 4Memory Incubator Funds Projekte vor, seid gespannt!

    Teilnehmen ist ganz einfach, ohne Voranmeldung über BBB: bbb.rlp.net/rooms/ttu-ktp-njp-

    #NFDI #NFDIrocks #NFDI4Memory #IncubatorFunds #LunchBreak #FDM #provenienzforschung #Bergbaumuseum #MaschinellesSehen #PythonPackage

  23. Sehen wir uns morgen in der Lunch Break @ 4Memory Incubator Funds?

    Von 12:30 bis 13:30 Uhr stellen das Deutsche Bergbau-Museum Bochum & Koordinationsstelle für Provenienzforschung in NRW die nächsten beiden 4Memory Incubator Funds Projekte vor, seid gespannt!

    Teilnehmen ist ganz einfach, ohne Voranmeldung über BBB: bbb.rlp.net/rooms/ttu-ktp-njp-

    #NFDI #NFDIrocks #NFDI4Memory #IncubatorFunds #LunchBreak #FDM #provenienzforschung #Bergbaumuseum #MaschinellesSehen #PythonPackage

  24. Sehen wir uns morgen in der Lunch Break @ 4Memory Incubator Funds?

    Von 12:30 bis 13:30 Uhr stellen das Deutsche Bergbau-Museum Bochum & Koordinationsstelle für Provenienzforschung in NRW die nächsten beiden 4Memory Incubator Funds Projekte vor, seid gespannt!

    Teilnehmen ist ganz einfach, ohne Voranmeldung über BBB: bbb.rlp.net/rooms/ttu-ktp-njp-

    #NFDI #NFDIrocks #NFDI4Memory #IncubatorFunds #LunchBreak #FDM #provenienzforschung #Bergbaumuseum #MaschinellesSehen #PythonPackage

  25. Sehen wir uns morgen in der Lunch Break @ 4Memory Incubator Funds?

    Von 12:30 bis 13:30 Uhr stellen das Deutsche Bergbau-Museum Bochum & Koordinationsstelle für Provenienzforschung in NRW die nächsten beiden 4Memory Incubator Funds Projekte vor, seid gespannt!

    Teilnehmen ist ganz einfach, ohne Voranmeldung über BBB: bbb.rlp.net/rooms/ttu-ktp-njp-

    #NFDI #NFDIrocks #NFDI4Memory #IncubatorFunds #LunchBreak #FDM #provenienzforschung #Bergbaumuseum #MaschinellesSehen #PythonPackage