Joe,
While most of your style suggestions are reasonable, I would actually
recommend the opposite of the first point you make in (a)., especially
if you're trying to write generic reusable code.
> For example, an item count is always an integer, but a distance is always a
> float.
This is close
Hello Ralf,
Thank you for the resources, they were very helpful.
I am done setting up the environment and I'm looking forward to making
contributions.
Thank you,
Joyce.
On Mon, May 6, 2019 at 8:57 PM Ralf Gommers wrote:
> Hi Ngoran, welcome!
>
>
> On Sun, May 5, 2019 at 10:53 AM Joyce Tirnyuy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
On behalf of the SciPy development team I'm pleased to announce
the release candidate SciPy 1.3.0rc2. Please help us test this pre-release.
The primary motivation for the second release candidate to is to update
wheels to use a more recent Op
I have a handout for my PHZ 3150 Introduction to Numerical Computing
course that includes some rules:
(a) All integer-valued floating-point numbers should have decimal points
after them. For
example, if you have a time of 10 sec, do not use
y = np.e**10 # sec
use
y = np.e**10. # sec
instea
Oops,
Somehow that got sent before I was done. (Like my use of the passive voice
there?)
Here is a complete message:
Do any of you know of a style guide for computational / numpy code?
I don't mean code that will go into numpy itself, but rather, users code
that uses numpy (and scipy, and...)
