Skip to content

Issues: chapel-lang/pychapel

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

24 Open 9 Closed
24 Open 9 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Error installing from source with pych -k
#98 opened Apr 3, 2018 by buddha314
3
Note for Chapel release 1.17.0 area: BTR
#89 opened Jan 24, 2018 by awallace-cray
1
Core dump from PyChapel when returning string type: Bug type: Feature Request
#81 opened Aug 8, 2017 by buddha314
4
Improve documentation on pyChapel return types
#80 opened Aug 3, 2017 by buddha314
17
Error on pych --compile type: Bug type: Feature Request
#78 opened Aug 3, 2017 by buddha314
15
Don't require reinstallation of PyChapel when .chpl files are updated type: Bug type: Feature Request
#77 opened Aug 3, 2017 by buddha314
Simplify installation of pych with Brew or Pip area: BTR
#75 opened Jul 19, 2017 by buddha314
51
Restore support for Numpy sparsely packed arrays help wanted type: Bug
#67 opened Mar 29, 2017 by lydia-duncan
Improve Installation of Chapel dependency help wanted type: Feature Request
#62 opened Nov 30, 2016 by lydia-duncan
3 tasks
4
Error while pych --check
#48 opened Mar 6, 2016 by SilentFlame
7
Non gcc/linux64 portability issues
#46 opened Jan 27, 2016 by ronawho
12
Testing is not portable to non linux64 platforms
#45 opened Jan 27, 2016 by ronawho
Fail after install
#42 opened Jun 20, 2015 by russel
12
Movement of chapel source code causes same directory modules to be ignored question type: Feature Request
#39 opened Jan 21, 2015 by lydia-duncan
Ability to share names between bfiles and sfiles type: Bug
#36 opened Jan 19, 2015 by lydia-duncan
Materialization conflict type: Bug
#31 opened Jan 15, 2015 by lydia-duncan
Bug in modularizing Chapel file type: Bug
#15 opened Jan 2, 2015 by lydia-duncan
3
Allow users to specify name of module question type: Feature Request
#14 opened Jan 2, 2015 by lydia-duncan
3
Do we want the ability to import a specific module rather than the whole file? question type: Feature Request
#10 opened Dec 10, 2014 by lydia-duncan
Allow where clauses in Chapel function declarations type: Feature Request
#9 opened Dec 10, 2014 by lydia-duncan
Expand the number of types that can cross the Python-Chapel divide Release priority type: Feature Request
#8 opened Dec 10, 2014 by lydia-duncan
4
Expand Chapel settings that work with this feature type: Feature Request
#7 opened Dec 10, 2014 by lydia-duncan
1
Chapel function declarations must fully specify their type type: Feature Request
#6 opened Dec 10, 2014 by lydia-duncan
Add more tests help wanted type: Feature Request
#5 opened Dec 10, 2014 by lydia-duncan
2
ProTip! Add no:assignee to see everything that’s not assigned.