semvec/pypi-packages huggingface dataset:
pyFC 0.1.7
Fractal cube generator, analyzer and visualizer
Keywords: clouds,astrophysics,simulation,hydrodynamics,cfd,initial conditions,fractal

pyFC: A Fractal cube generator, analyzer and visualizer
-------------------------------------------------------

pyFC is a module to construct "fractal cubes" that are useful for initial conditions in hydrodynamical simulations representing a dense, inhomogeneous component embedded in a more tenuous smooth background. Examples include clouds in earth's athmosphere or the multiphase interstellar medium in galaxies. 

Classes and functions are provided to create and visualize single-point lognormal, two-point fractal fields, statistics often associated with turbulent, dense condensations.

The method of creating lognormal "fractal cubes" was conceived by `Lewis & Austin (2002)`_ for the modeling of clouds in the earth's atmosphere. The scheme of this code is based on that outlined in their paper.

.. _Lewis & Austin (2002): https://ams.confex.com/ams/11AR11CP/techprogram/paper_42772.htm
tornado-rest-easy 0.1
library for easy restful APIs in tornado

# tornado_rest_easy - RESTful extension for tornado

This library aims to make it quicker and easier to define a RESTful API in tornado. Originally inspired by github.com/rancavil/tornado-rest.

## Installation
```
pip install tornado_rest_easy
```

## Usage

```python
from tornado_rest_easy import RestfulHandler, RestfulMetaType, get, post


class WidgetHandler(RestfulHandler, metaclass=RestfulMetaType):

    @get('/widgets')
    def all_widgets(self):
        return [widget1, widget2, ...]

    @get('/widgets/<int:id>')
    def get_widget(self, id):
        return widgets[id]

    @post('/widgets'):
    def add_widget(self):
        return 'Widget added'

app = Application(WidgetHandler.get_handlers(dict(db=db))
```

## License
New BSD. See [license](https://github.com/postelrich/tornado_rest_easy/blob/master/LICENSE).
racketinterpreter 0.1.0
An interpreter for Racket
Requires Python: >=3.7

# Racket Interpreter

An interpreter written for Racket, more specifically the student languages which are (almost) a subset of the language.
These student languages are what first-semester, computer-science students at Northeastern learn to program in.
The end goal of this project is to successfully interpret the code I wrote for a homework assignment regarding graphs.

[![Build Status](https://travis-ci.org/ZibingZhang/racket-interpreter.svg?branch=master)](https://travis-ci.org/ZibingZhang/racket-interpreter)
<img src="https://img.shields.io/badge/license-MIT-brightgreen"></img>
<img src="https://img.shields.io/badge/python-3.7%2B-blue"></img>

## Table of Contents

  * [Getting Started](#getting-started)
    * [Prerequisites](#prerequisites)
    * [Installing & Running](#installing--running)
  * [Licence](#licence)
  * [Acknowledgments](#acknowledgments)
  * [Documentation](#documentation)

## Getting Started

There is no IDE nor does the interpreter read from a text file... yet.
That being said, here are the steps to set up and get the interpreter running.

### Prerequisites

The only prerequisite is to have Python 3.7+.

### Installing & Running

Clone the repository locally and execute the source module as a script.
```
git clone https://github.com/ZibingZhang/racket-interpreter.git
cd racket-interpreter
python racketinterpreter/__init__.py
```

To change the code that is being interpreted, change the value of `text` in `racketinterpreter/__init__.py`.

### Testing

```
python -m unittest
```

## Licence

This project is licensed under the MIT license.

## Acknowledgments

This initially started as an adaptation of Ruslan Spivak's [tutorial](https://ruslanspivak.com/lsbasi-part1/) for writing an interpreter.
Most of the structure of this codebase come from the tutorial, but as I've begun to understand his design decisions better I've been able to change and adapt them to fit this project.
This [template](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2) has also been helpful in understanding how to format a README and what I should include.

## Documentation

I've decided to keep the documentation in the same README for the time being.