How to prevent bloom-release from creating dependencies on python pip packages?

edit

I'm releasing packages locally using bloom-release.

One of my package has a dependency on a python pip package (svgpathtools). I have added this package to rosdep so that it can be resolved easilly when compiling the project.

So my package.xml contains:

<depend>svgpathtools-pip</depend>

This package has a few other source dependencies that are manually added in the release.bash script of the project.

When I release the package it can't be installed because it contains a dependency on the svgpathtools package, this can be seen in the debian/control file:

Source: ros-melodic-ram-utils
Section: misc
Priority: extra
Maintainer: Victor Lamoine <victor.lamoine@gmail.com>
Build-Depends: debhelper (>= 9.0.0), libyaml-cpp-dev, ros-melodic-catkin, ros-melodic-eigen-conversions, ros-melodic-geometry-msgs, ros-melodic-message-generation, ros-melodic-message-runtime, ros-melodic-ram-msgs, ros-melodic-rosbag, ros-melodic-roscpp, ros-melodic-roslib, ros-melodic-rospy, ros-melodic-rostest, ros-melodic-std-msgs, ros-melodic-tf2-ros, ros-melodic-unique-id, ros-melodic-uuid-msgs, svgpathtools
Homepage: 
Standards-Version: 3.9.2

Package: ros-melodic-ram-utils
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, libyaml-cpp-dev, ros-melodic-eigen-conversions, ros-melodic-geometry-msgs, ros-melodic-message-generation, ros-melodic-message-runtime, ros-melodic-ram-msgs, ros-melodic-rosbag, ros-melodic-roscpp, ros-melodic-roslib, ros-melodic-rospy, ros-melodic-std-msgs, ros-melodic-tf2-ros, ros-melodic-unique-id, ros-melodic-uuid-msgs, svgpathtools
Description: Additive manufacturing miscellaneous utilities

svgpathtools is not a debian package so it cannot be resolved by dpkg, leading to a package that cannot be installed.

Is there a way to tell bloom-release ignore this package dependency? I provide instructions to the end users so that they install svgpathtools through pip manually.