I will start with a bit of a frame challenge: it does not matter what you call the two vertices of an edge in a digraph. Even less important is how you label these nodes in your code. You can adopt whatever convention you like. Some conventions will be easier for others to read and understand than others, but the choice is really up to you. In this sense, there is no one "right" answer (though there are infinitely many "wrong" answers, as there are a lot of things you could do to make your code or your writing less readable).
That being said, if you are trying to produce something readable for others, it would probably be reasonable to adopt a standard which is descriptive. Some possibilities include the following:
Let $u$ and $v$ be two nodes in a digraph and let $e = (u,v)$ denote the directed edge which goes from $u$ to $y$. Then
Wikipedia suggests that $u$ is the tail and $v$ is the head of $e$;
this set of notes from Carnegie Mellon uses the terms origin and destination of $e$ for the nodes $u$ and $v$, repectively;
as suggested by JMoravitz in a now-deleted comment, from_node and to_node might be reasonable variable or function names in a programming context, e.g. the node u is the output of from_node(e), while v is the output of to_node(e);
it seems natural to me to call $u$ the start of $e$ and to call $v$ the end of $e$, though some quick Googling indicates that this terminology is likely rather rare; on the other hand, I seem to recall writing $s(E)$ and $e(E)$ to denote the start and end of an edge $E$ in a graph theory course I took maybe 15 years ago, so perhaps there is precedent;
Mathworks calls $u$ the source of $e$, and $v$ the target of $e$ (note that this nomenclature is also common in category theory: a morphism between objects has a source and target).