Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Create/suggest developer environment

未关闭
#17 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
jupyter, node.js, plotly, python

调研方向

Start by reviewing the existing developer setup guidance and reproducing the reported Python, Node, and conda-based Jupyter Book issues. Compare approaches for building, running, and testing all PolicyEngine products, then document one reliable shared environment and verify that notebook Plotly outputs work.

由索引模型根据 Issue 内容生成。

描述

Developers have run into issues with environments in two main ways:

  • Python version being non-3.7 (e.g. conda's default of 3.8)
  • Node's version being non-14

We've thus far suggested a Python 3.7 conda environment and using nvm to install node 14.

But I've also hit an issue building jupyter-book notebooks from a conda environment, as that seems to break the plotly outputs.

What's the most simple and reliable approach that developers can take to ensure they can build, run, and test all PolicyEngine products? Should we use conda? Basically, how can we get all developers to have the most similar environment to @nikhilwoodruff? :)

主要语言
Makefile
星标
1
派生
3
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PolicyEngine/policyengine.dev 的其他 Issue

查看 PolicyEngine/policyengine.dev 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。