This commit is contained in:
2019-09-15 13:15:15 -04:00
parent 23655d2b93
commit bb2c37031e
14 changed files with 117 additions and 3 deletions
+1 -2
View File
@@ -1,3 +1,2 @@
.vscode/settings.json
bashf.egg-info/*
bashfile.egg-info/*
bake.egg-info/*
+53
View File
@@ -0,0 +1,53 @@
Metadata-Version: 2.1
Name: bashf
Version: 0.1.0
Summary: The familar Make / Bash hybrid.
Home-page: https://github.com/kennethreitz/bashfile
Author: Kenneth Reitz
Author-email: me@kennethreitz.org
License: MIT
Description:
# `bashf`— Kinda like Make & Bash, combined.
I love using `Makefile`s for one-off tasks in projects. The problem with doing this, is you can't use familiar bashisms when doing so, as GNU Make doesn't use the familiar Bash sytnax. This project seeks to bridge these works.
## Example `Bashfile`
To be improved:
```make
echo:
cat Bashfile
format:
black .
full-install: system-deps install
install: node-deps python-deps
python-deps:
# Example of comments
pipenv install
node-deps:
yarn install
system-deps:
brew install pipenv
```
Unlike `Makefile`, either tabs or 4 spaces can be used.
## Installation
Install `bashf` via:
$ brew install kennethreitz/-/bashf --head
Platform: UNKNOWN
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: Implementation :: CPython
Classifier: Programming Language :: Python :: Implementation :: PyPy
Requires-Python: >=3.6.0
Description-Content-Type: text/markdown
+12
View File
@@ -0,0 +1,12 @@
README.md
setup.py
bashf/__init__.py
bashf/bash.py
bashf/bashfile.py
bashf/cli.py
bashf.egg-info/PKG-INFO
bashf.egg-info/SOURCES.txt
bashf.egg-info/dependency_links.txt
bashf.egg-info/entry_points.txt
bashf.egg-info/requires.txt
bashf.egg-info/top_level.txt
+1
View File
@@ -0,0 +1 @@
+3
View File
@@ -0,0 +1,3 @@
[console_scripts]
bashf = bashf.cli:entrypoint
+3
View File
@@ -0,0 +1,3 @@
click
delegator.py
crayons
+1
View File
@@ -0,0 +1 @@
bashf
+23
View File
@@ -0,0 +1,23 @@
Metadata-Version: 2.1
Name: bashfile
Version: 0.1.0
Summary: Make + Bash
Home-page: https://github.com/kennethreitz/bashfile
Author: Kenneth Reitz
Author-email: me@kennethreitz.org
License: MIT
Description:
# Bashfile: Like Make + Bash, Combined.
I love using `Makefile`s for one-off tasks in projects. The problem with doing this, is you can't use familiar bashisms when doing so, as GNU Make doesn't use the familiar Bash sytnax. This project seeks to bridge these works.
Platform: UNKNOWN
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: Implementation :: CPython
Classifier: Programming Language :: Python :: Implementation :: PyPy
Requires-Python: >=3.6.0
Description-Content-Type: text/markdown
+10
View File
@@ -0,0 +1,10 @@
README.md
setup.py
bashf/__init__.py
bashf/cli.py
bashfile.egg-info/PKG-INFO
bashfile.egg-info/SOURCES.txt
bashfile.egg-info/dependency_links.txt
bashfile.egg-info/entry_points.txt
bashfile.egg-info/requires.txt
bashfile.egg-info/top_level.txt
+1
View File
@@ -0,0 +1 @@
+3
View File
@@ -0,0 +1,3 @@
[console_scripts]
bashf = bashfile.cli:entrypoint
+4
View File
@@ -0,0 +1,4 @@
click
delegator.py
crayons
bash.py
+1
View File
@@ -0,0 +1 @@
bashf
+1 -1
View File
@@ -104,7 +104,7 @@ setup(
packages=find_packages(exclude=["tests", "*.tests", "*.tests.*", "tests.*"]),
# If your package is a single module, use this instead of 'packages':
# py_modules=['mypackage'],
entry_points={"console_scripts": ["bashf=bashf.cli:entrypoint"]},
entry_points={"console_scripts": ["bake=bake.cli:entrypoint"]},
install_requires=REQUIRED,
extras_require=EXTRAS,
include_package_data=True,