Yashotantra Academy logo
← Vyper theorytheory 0/50 · 0%
level 1
Curious · 0 XP
streak
0d
perfect
0
badges
0

100 XP to Apprentice

Foundations · easy

2. Version pragma and file layout

Pinning the compiler version and structuring a Vyper module.

1 min read3 questionsup to 50 XPtopic 2/50

Read in another language

AI translates the explanation and quiz text while preserving code and answer scoring.

Every Vyper file should declare the compiler version it was written for using a comment pragma. This isn't optional style — the compiler refuses to build if the installed version falls outside the stated range.

A typical file layout is: version pragma, imports/interfaces, state variables, events, constructor, then external and internal functions grouped by purpose.

# @version ^0.3.10

from vyper.interfaces import ERC20

owner: public(address)
token: public(address)

event Deposited:
    amount: uint256

Unlike Solidity's `pragma solidity`, Vyper's version comment must start with `# @version` and is checked strictly against the installed compiler.

How to study this topic

  1. 1. Read the explanation once end to end, skipping the code.
  2. 2. Re-read the code snippets and say out loud what each line does.
  3. 3. Answer the quiz without scrolling back — that is the real check.
  4. 4. Read every explanation, even for the answers you got right.

Scoring

  • · Up to 30 XP from quiz accuracy.
  • · +15 XP for a perfect first attempt.
  • · +5 XP while a 3-day streak is running.
  • · 75% or higher marks the topic complete.

Check your understanding

  1. 1. How is the compiler version declared in Vyper?

  2. 2. What happens if the installed compiler doesn't match the pragma?

  3. 3. Where do interface imports typically go in a Vyper file?

Badges

First light
Pass your first topic
Sharp shooter
3 perfect first-try quizzes
On a roll
Study 3 days in a row
Week warrior
Study 7 days in a row
Grinder
Earn 500 XP
Deep diver
Earn 1500 XP