Skip to content
#

infrastructure

Here are 1,640 public repositories matching this topic...

backstage
marvin-robot
marvin-robot commented May 17, 2021

Opened from the Prefect Public Slack Community

elliot: Hey folks is anyone else getting a deprecation warning on marshmallow? Something like:

...
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198: RemovedInMarshmallow4Warning: Passing fi

Saves up to 90% of AWS EC2 costs by automating the use of spot instances on existing AutoScaling groups. Installs in minutes using CloudFormation or Terraform. Convenient to deploy at scale using StackSets. Uses tagging to avoid launch configuration changes. Automated spot termination handling. Reliable fallback to on-demand instances.

  • Updated Jun 19, 2021
  • Go
moreati
moreati commented Feb 14, 2021

A number of modules, and scripts in the test suite start with

#!/usr/bin/env python

In general it is better to use

#!/usr/bin/env python

because that allows execution inside a virtualenv, or when python is installed elsewhere, e.g. /usr/loca/bin/python.

There may be cases in which we really do want to hard code the path - for instance testing detection/selection of `

Improve this page

Add a description, image, and links to the infrastructure topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the infrastructure topic, visit your repo's landing page and select "manage topics."

Learn more