# Confused about change in axes() for v1.1

**URL:** <https://discourse.julialang.org/t/confused-about-change-in-axes-for-v1-1/20318>\
**Category:** General Usage\
**Created:** [January 31, 2019, 4:00pm UTC](https://discourse.julialang.org/t/confused-about-change-in-axes-for-v1-1/20318 "2019-01-31T16:00:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tobydriscoll](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tobydriscoll/32/1843_2.png) [@tobydriscoll](https://discourse.julialang.org/u/tobydriscoll)\
**Post date:** [January 31, 2019, 4:00pm UTC](https://discourse.julialang.org/t/confused-about-change-in-axes-for-v1-1/20318/1 "2019-01-31T16:00:46Z")

</div>

I was surprised to see that I got a new error in 1.1 that did not occur in 1.0. The culprit was this change in `axes`:

```julia
driscoll@~\> julia-1.0
               _
  | | |_| | | | (_| | | Version 1.0.3 (2018-12-18)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release

julia> axes( (1,2) )
Base.OneTo(2)
^D

driscoll@~> julia-1.1
               _
  | | |_| | | | (_| | | Version 1.1.0 (2019-01-21)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release

julia> axes( (1,2) )
(Base.OneTo(2),)

```

It seems that this change was introduced in commit [817f6fc](https://github.com/JuliaLang/julia/commit/817f6fc7eebab4e6995e6b571ddaca349f64d46e#diff-fd99c9a15dadc23d9200069dadafb8bb), with the message “fix definition of axes”. I don’t see any mention of this in the 1.1.0 NEWS.md file.

Am I wrong in thinking about this as a breaking change? Why was the 1.0 behavior considered broken?

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [January 31, 2019, 4:18pm UTC](https://discourse.julialang.org/t/confused-about-change-in-axes-for-v1-1/20318/2 "2019-01-31T16:18:53Z")

</div>

The previous behavior was _definitely_ a bug, but you’re right — we should have made sure to flag this as a minor change. Sorry this caught you out.

The definition of `axes` is to return a tuple with one axis per dimension. Tuples themselves are only one-dimensional, so it should return a tuple with one element in it. This change brings `axes((1, 2))` in line with `axes([1,2])`.