Feature: Quack Quack - Application Runner

[socek]

Submitting Author: (@socek)
Package Name: @socek
One-Line Description of Package: Application Runner using dependency injection for gathering settings and connecting to services
Repository Link (if existing): https://github.com/socek/quackquack
EiC: @NickleDave

---

Code of Conduct & Commitment to Maintain Package

• I agree to abide by pyOpenSci's Code of Conduct during the review process and in maintaining my package after should it be accepted.
• I have read and will commit to package maintenance after the review as per the pyOpenSci Policies Guidelines.

Description

Community Partnerships

We partner with communities to support peer review with an additional layer of
checks that satisfy community requirements. If your package fits into an
existing community please check below:

• Astropy: My package adheres to Astropy community standards
• Pangeo: My package adheres to the Pangeo standards listed in the pyOpenSci peer review guidebook

Scope

• Please indicate which category or categories this package falls under:

  • Data retrieval
  • Data extraction
  • Data processing/munging
  • Data deposition
  • Data validation and testing
  • Data visualization
  • Workflow automation
  • Citation management and bibliometrics
  • Scientific software wrappers
  • Database interoperability

Domain Specific

• Geospatial
• Education

---

• Explain how and why the package falls under these categories (briefly, 1-2 sentences).

• For community partnerships, check also their specific guidelines as documented in the links above. Please note any areas you are unsure of:

• Who is the target audience and what are the scientific applications of this package?

• Are there other Python packages that accomplish similar things? If so, how does yours differ?

• Any other questions or issues we should be aware of:

P.S. Have feedback/comments about our review process? Leave a comment here
Hoping to hear from your team soon.

Original text below

Submitting Author

@socek

Current Maintainers

@socek

Package Name

Quack Quack

One-Line Description of Package

Application Runner using dependency injection for gathering settings and connecting to services

Repository Link

https://github.com/socek/quackquack

Version submitted

1.2.0

Documentation url

https://qqpy.org/

[NickleDave]

Welcome @socek to pyOpenSci and thank you for your submission.

Could you tell us a little more about how you found out about us?

I see you've been working hard on Quack Quack for a while but at first glance it looks like it might not be in scope--the packages we review need to have a clear application to science specifically.
You can read more about package scope here: https://www.pyopensci.org/software-peer-review/about/package-scope.html

Happy to talk more with you here about it and figure out how we can help you

[socek]

Hello.

Could you tell us a little more about how you found out about us?

There was a small conference in Poland (PyTech Summit) and some guy talked about you.

the packages we review need to have a clear application to science specifically.

There is no clear application to science specifically. But this is an application initializer and every application needs some initalization, so I decided it worth a try. If it's consider a "out of scope" that's fine. I will try elsewhere.

Thanks anyway. (:

[NickleDave]

There was a small conference in Poland (PyTech Summit) and some guy talked about you.

Ah that would be @szymonMolinski. Well, cześć friend, glad we could be introduced.

this is an application initializer and every application needs some initalization

You are totally right, but that's what makes it out of scope for us, that it's a general programming tool.

I think the approach is interesting. Do you know this book? https://www.cosmicpython.com/. If not, it might give you some food for thought. I can imagine Quack Quack being a good tool for a services layer where you want to do dependency injection.

I wonder if you could get feedback on https://codereview.stackexchange.com/ or by posting on
https://discuss.python.org/?

[NickleDave]

I will go ahead and close this, thank you again for your interest @socek