Skip to content

Commit 2e0741e

Browse files
committed
🔖 Release v0.2.0
1 parent afcf012 commit 2e0741e

File tree

4 files changed

+7
-4
lines changed

4 files changed

+7
-4
lines changed

.gitignore

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ ipython_config.py
8989
# However, in case of collaboration, if having platform-specific dependencies or dependencies
9090
# having no cross-platform support, pipenv may install dependencies that don't work, or not
9191
# install all needed dependencies.
92-
#Pipfile.lock
92+
Pipfile.lock
9393

9494
# PEP 582; used by e.g. github.com/David-OConnor/pyflow
9595
__pypackages__/
@@ -127,3 +127,6 @@ dmypy.json
127127

128128
# Pyre type checker
129129
.pyre/
130+
131+
# Other
132+
.vscode/

README-ja.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ $ amplify-bench stats preset_20230803_223440.json
165165
| `variables` | `object` | ジョブで使用可能な変数の定義 (Optional) |
166166
| `imports` | `array[string]` | ユーザー定義の問題のファイルパス (Optional) |
167167

168-
`variables` キーに与える変数定義は `jobs` 内で参照することが出来ます。この時、`$` から始まる文字列は変数名として扱われます。例えば次のように全ての問題に共通する設定を与えるときに有用です。
168+
ファイルの中の `$` から始まる文字列は変数名として扱われます。最初に実行時の環境変数によって展開され、その後 `variables` キーに与えた変数定義が `jobs` 内で参照されます。例えば次のように全ての問題に共通する設定を与えるときに有用です。
169169

170170
```yaml
171171
variables:

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ A job set file consisted of JSON objects with the following keys. The schema of
165165
| `variables` | `object` | definitions of variables used in `jobs` (Optional) |
166166
| `imports` | `array[string]` | User-defined problem file path (Optional) |
167167

168-
Variable definitions for the `variables` key can be referenced in `jobs`. A string starting with `$` is treated as a variable name. This is useful, for example, to specify a setting that is commonly used in multiple jobs
168+
Strings in the file that begin with `$` are treated as variable names. Variables are first expanded by the environment variables at runtime, then the variable definitions given in the `variables` key are referenced in `jobs`. This is useful, for example, to specify a setting that is commonly used in multiple jobs
169169

170170
```yaml
171171
variables:

setup.cfg

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[metadata]
22
name = amplify-bench
3-
version = 0.1.3
3+
version = 0.2.0
44
author = Fixstars Corporation, Fixstars Amplify Corporation
55
author_email = "Yoshiki Matsuda" <[email protected]>
66
maintainer = Yoshiki Matsuda, Hiroki Kawahara, Kosuke Suzuki

0 commit comments

Comments
 (0)